Interactive Transaction Center Interface

ABSTRACT

A transaction module having a summary interface is provided as part of a software suite for enabling viewing and manipulation of multiple categories of aggregated data compiled from a plurality of data sources and accessible through a single interfacing node operated on a data-packet-network. The transaction module comprises, an interactive main interface accessible through the summary interface, the main interface for listing new transactions related to registered financial accounts, an interactive history link embedded in the main interface for providing access to a secondary interface for viewing transaction history, an interactive menu provided within the main interface for assigning categories to the listed transactions, an interactive save feature for saving category assignments to the listed transactions; a interactive bill-payment link provided within the main interface for linking the interface to a bill-payment module and an interactive transfer-funds link provided within the summary interface of the module for linking the summary face of the module to a secondary interface for transferring funds from one account to another. A user operating the main interface from a remote node having access to the data-packet-network may view all transactions according to option of category, account, and time period.

CROSS-REFERENCE TO RELATED DOCUMENTS

The present application is a continuation of co-pending application Ser.No. 10/892,078, filed Jul. 14, 2004, which is a divisional applicationof Ser. No. 09/826,747, filed Apr. 4, 2001 and issued as U.S. Pat. No.6,859,212 on Feb. 22, 2005, which is a continuation-in-part (CIP) topatent application Ser. No. 09/698,708, filed on Oct. 27, 2000 andissued as U.S. Pat. No. 7,672,879 on Mar. 2, 2010, which is a CIP topatent application Ser. No. 09/425,626, filed on Oct. 22, 1999 andissued as U.S. Pat. No. 6,802,042 on Oct. 5, 2004, which is a CIP to apatent application Ser. No. 09/323,598, filed on Jun. 1, 1999 and issuedas U.S. Pat. No. 6,199,077 on Mar. 26, 2001, which is a CIP to patentapplication Ser. No. 09/208,740, filed on Dec. 8, 1998 and issued asU.S. Pat. No. 6,412,073 on Jun. 25, 2002, disclosures of which areincorporated herein in their entirety by inclusion and reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention is in the field of Internet navigation includingvarious communication means and connection technologies. The presentinvention pertains more particularly to an interactive softwarefunctionality enabling management and transactional control includingcategorized viewing of personal transaction data including account datamaintained on behalf of users by an entity providing data compilation,aggregation, and summary services.

2. Discussion of the State of the Art

The information network known as the World Wide Web (WWW), which is asubset of the well-known Internet, is arguably the most complete sourceof publicly accessible information available. Anyone with a suitableInternet appliance such as a personal computer with a standard Internetconnection may access (go on-line) and navigate to information pages(termed web pages) stored on Internet-connected servers for the purposeof garnering information and initiating transactions with hosts of suchservers and pages.

Many companies offer various subscription services accessible via theInternet. For example, many people now do their banking, stock trading,shopping, and so forth from the comfort of their own homes via Internetaccess. Typically, a user, through subscription, has access topersonalized and secure WEB pages for such functions. By typing in auser name and a password or other personal identification code, a usermay obtain information, initiate transactions, buy stock, and accomplisha myriad of other tasks.

One problem that is encountered by an individual who has several or manysuch subscriptions to Internet-brokered services is that there areinvariably many passwords and/or log-in codes to be used. Often a samepassword or code cannot be used for every service, as the password orcode may already be taken by another user. A user may not wish to supplya code unique to the user such as perhaps a social security numberbecause of security issues, including quality of security that may varyfrom service to service. Additionally, many users at their own volitionmay choose different passwords for different sites so as to haveincreased security, which in fact also increases the number of passwordsa user may have.

Another issue that can plague a user who has many passwordedsubscriptions is the fact that they must bookmark many WEB pages in acomputer cache so that they may quickly find and access the variousservices. For example, in order to reserve and pay for airline travel, auser must connect to the Internet, go to his/her book-marks file andselect an airline page. The user then has to enter a user name andpassword, and follow on-screen instructions once the page is delivered.If the user wishes to purchase tickets from the WEB site, and wishes totransfer funds from an on-line banking service, the user must also lookfor and select the personal bank or account page to initiate a fundstransfer for the tickets. Different user names and passwords may berequired to access these other pages, and things get quite complicated.

Although this preceding example is merely exemplary, it is generallyknown that much work related to finding WEB pages, logging in withpasswords, and the like is required to successfully do business on theWEB.

A service known to the inventor and described in patent application Ser.No. 09/208,740 entitled “Method and Apparatus for Providing andMaintaining a User-Interactive Portal System Accessible via Internet orother Switched-Packet-Network”, provides a WEB service that allows auser to store all of his password protected pages in one location suchthat browsing and garnering information from them is much simplified. Afeature of the above service allows a user to program certain tasks intothe system such that requested tasks are executed by an agent (software)based on user instruction. The service stores user password and log-ininformation and uses the information to log-in to the user's sites, thusenabling the user to navigate without having to manually input log-in orpassword codes to gain access to the links.

The above-described service uses a server to present a user-personalizedapplication that may be displayed as an interactive home page thatcontains all of his listed sites (hyperlinks) for easy navigation. Theapplication lists the user's URL's in the form of hyperlinks such that auser may click on a hyperlink and navigate to the page wherein login, ifrequired, is automatic, and transparent to the user.

The application described above also includes a software agent that maybe programmed to perform scheduled tasks for the user includingreturning specific summaries and updates about user-account pages. Asearch function is provided and adapted to cooperate with the softwareagent to search user-entered URL's for specific content if such pagesare cached somewhere in their presentable form such as at the portalserver, or on the client's machine.

In addition to the features described above, patent application Ser. No.09/523,598 entitled “Method and Apparatus for Obtaining and PresentingWEB Summaries to Users” describes a software agent used in conjunctionwith a search function that is enabled to navigate to any URL or groupof URL's, provided as input by a user or otherwise deemed appropriate bythe service provider, for the purpose of providing summary informationregarding updated content for each URL, which may be presented as anHTML information-page to the user.

The above described service uses known site logic for navigating tospecific “chunks” of data contained in Web pages at the site. Logicscripts are prepared by knowledge workers operating on behalf of users.With such scripts, gatherer agents may navigate directly to dataportions that users are interested in.

Users who subscribe to many on-line services generally do all of theirbanking, investing, travel arranging, shopping, and so on while on-linewith the Internet. Having all of his or her services available at oneportal provides a convenience to a user in not having to remember aplurality of passwords, or to be required to physically log-on to eachsite. Similarly, the ability to obtain summary data associated withselected sites through one interface allows a user to greatly speed anydecision making process related to his or her on-line activity. However,summary information may not help a user with certain other concerns. Forexample, obtaining accurate financial information concerning his entireportfolio of banking and investments would require much user calculationdepending on the exact nature of the result desired. Similarly compilinga trend that reflects a user's on-line activity at a plurality ofshopping services may also require considerable calculation to beperformed by a user. Summary data presented in the above methods isgeneral in nature and reflects such as updates, status of orders, andthe like.

An Internet-connected portal system, known to the inventor, has a datarepository, a data-gathering system, a request processor, a plurality ofreport algorithms, and a report processor. The request processorreceives a request from a user and matches the request to an individualone of the report algorithms. The data-gathering subsystem accessesplural Internet sites associated with the user and extracts raw datatherefrom according to needs of the report algorithm. The reportprocessor processes the raw data according to the report algorithm intometa-summarized information defined by the report algorithm, and theportal system transmits the meta-summarized information as a report to adestination associated with the report request. In some cases there isan aggregated-data database in the data repository storing aggregateddata retrieved for specific users periodically, and the requestprocessor checks the aggregated-data database for needed data beforerequiring the data-gathering system to retrieve data from the associatedInternet sites. In the instance that the needed data is stored in theaggregated-data database, the report is prepared from the aggregateddata. Reports may be presented in a form such as to include text andgraphic formats.

In view of various functional enhancements including the ability toprovide calculative and solution-oriented reporting, it has occurred tothe inventor that a single interface, through which summary and detaileddata may be viewed and manipulated must be provided that isuser-friendly, compact and interlinked in terms of request-to-resultfunctionality wherein access and request actions may be performed byworking within any category or department of data that may be availableto be viewed through the interface. Current and prior-art interactiveinterface software used with typical data presentation services lacksthe flexibility of providing multiple points of intractability withinthe interface as well as enabling cross-solution implementation acrossmultiple categories of data viewable through the interface.

The above challenges exist with prior-art services in part because theylack much of the interactive capability required in order to enable afully functional data interface, especially one that interfaces a userwith a wide range of disparate data categories.

A software suite known to the inventor for enabling viewing andmanipulation of multiple categories of aggregated data compiled from aplurality of data sources and accessible through a single interfaceoperated on a data-packet-network is provided. The data sources areavailable for direct network-access through multiple access pointsavailable from within the interface. The software suite comprises, acalendar module having at least one display interface for enablingviewing and manipulation of time and date-sensitive calendar data, atransaction module having at least one display interface for enablingviewing and manipulation of financially oriented account data, aportfolio tracking module having at least one display interface forenabling viewing and manipulation of investment oriented account data, anet-worth reporting module having at least one display interface fordisplaying a solution-oriented net-worth report compiled from theaggregated, a bill-payment module having at least one display interfacefor enabling viewing and initiation of payment action regarding currentbilling data and an account-alert module having at least one displayinterface for reporting time and event sensitive account alerts relatedto changes in account data due to occurring events or pre-configuredtime parameters.

A user operating a remote node connected to the network of a serverhosting the software suite may view and manage personal data. Inpreferred embodiments, the data requests received at the server from theuser regarding data management and manipulation are performed by proxywhen such requests require navigation and/or solution orientedcalculations and presentations. In this specification further novelfunctions related to the transaction management and categorized viewingcapabilities of the transaction module described above are taught inenabling detail.

SUMMARY OF THE INVENTION

In a preferred embodiment of the present invention, a transaction modulehaving a displayable summary interface is provided as part of a softwaresuite for enabling viewing and manipulation of multiple categories ofaggregated data compiled from a plurality of data sources and accessiblethrough a single interfacing node operated on a data-packet-network. Thetransaction module comprises, an interactive main interface accessiblethrough the summary interface, the main interface for listing newtransactions related to registered financial accounts, an interactivehistory link embedded in the main interface for providing access to asecondary interface for viewing transaction history, an interactive menuprovided within the main interface for assigning categories to thelisted transactions, an interactive save feature for saving categoryassignments to the listed transactions, an interactive bill-payment linkprovided within the main interface for linking the interface to abill-payment module and an interactive transfer-funds link providedwithin the summary interface of the module for linking the summary faceof the module to a secondary interface for transferring funds from oneaccount to another.

A user operating the main interface from a remote node having access tothe data-packet-network may view all transactions according to option ofcategory, account, and time period.

In a preferred embodiment, the transaction module is accessed throughthe

Internet network. In this aspect, the plurality of data sources areservices accessible over the Internet and subscribed to by the operatinguser. Also in this aspect, the accessible services are hosted in fileservers addressed on the Internet network. In one embodiment, theabove-mentioned remote node is a personal computer with accessibility tothe Internet and the summary, main and secondary interfaces are providedin the form of hyper-text-markup-language. In another embodiment, theremote node is a cellular telephone with accessibility to the Internet.In still another embodiment, the remote node is a hand-held computerwith accessibility to the Internet.

In all aspects, the interactive menu within the main interface containsa selectable list of transaction categories including food and beverage,utilities, home, auto, charitable contribution, and entertainment. Inthis same aspect, the secondary interface invoked from the interactivehistory link contains a plurality of interactive menus, the menuscontaining selectable options for categorical viewing of transactionhistory. The selectable options enable viewing transactions by aspecific account, a specified timeframe, and by a selected category, theoptions are selectable for ordering combinations of criteria forproducing a transaction view.

In one aspect, the transaction module further comprises a chartingfeature for rendering a transactional view in the form of a graphicschart. In this aspect, the graphics chart ordered and displayed isalterable by changing selection of options within the plurality ofinteractive menus in the secondary interface and refreshing theinterface.

In another aspect of the present invention, an interactive transactionviewing system for enabling online viewing of itemized transactionsperformed across disparate on-line accounts and services over adata-packet-network is provided. The interactive viewing systemcomprises, a first server node connected to the network, the server nodeproviding a service-access-point for accessing users, a second servernode connected to the network and accessible to the first server node,the second server node providing automated navigation, data procurement,and data aggregation on behalf of the accessing users, a plurality ofserver nodes connected to the network and accessible to the secondserver node, the server node functioning as data sources for the dataprocurement and aggregation and a transaction viewing software interfaceinstalled on the first server node, the interface accessible to theaccessing users connected to the network by respective remote computernodes.

Users accessing the first server node from the remote computer nodesinteract with the transaction-viewing interface for the purpose ofviewing transactions according to ordered category and graphicalpresentation option. The transactions are entered manually or detectedautomatically through system updates and or user requests. Additionally,the transactions are compiled and aggregated by proxy using cooperativefunctions of the first and second server nodes.

In a preferred embodiment, the system is implemented on the Internetnetwork. In one aspect, the first server node is a portal serverproviding personalized interfaces of the form ofhyper-text-markup-language interfaces. In this aspect, the on-lineaccounts and services are accessible over the Internet and subscribed toby the accessing users. In one embodiment, the remote computer nodes arepersonal computers with accessibility to the Internet. In anotherembodiment, the remote computer nodes are cellular telephones withaccessibility to Internet. In still another embodiment, the remotecomputer nodes are hand-held computers with accessibility to theInternet. In another aspect of the interactive transaction-viewingsystem, the second server node stores aggregated data in a connecteddata repository held externally from the server. In another aspect, thetransaction-viewing software interface is linked to at least onesecondary interface provided in the form of hyper-text-markup-language.In still another aspect, an interactive menu is accessible from withinthe transaction viewing interface, the menu containing a selectable listof transaction categories including food and beverage, utilities, home,auto, charitable contribution, and entertainment, each categoryassignable to a selected transaction listed in the interface, theassignments savable to the system.

Also in one aspect, a secondary interface accessible from interactionwithin the main interface contains a plurality of interactive menus, themenus containing selectable options for categorical viewing oftransaction history. The selectable options enable viewing transactionsby a specific account, a specified timeframe, and by a selectedcategory. Additionally, the options are selectable for orderingcombinations of criteria for producing a transaction view, wherein thetransaction view comprises an ordered history view.

In another aspect, the transaction-viewing system further comprises acharting feature associated with the selectable options. The chartingfeature renders a transactional view in the form of a graphics chart. Inthis aspect, the graphics chart ordered and displayed is alterable bychanging selection of options within the plurality of interactive menusin the secondary interface and refreshing the interface.

In another aspect of the present invention, a method for ordering andviewing transaction data presented in an interactive transaction-viewinginterface accessible through a data-packet-network is provided. Themethod comprises the steps of: (a) accessing an interactivetransaction-viewing interface from a remote node connected to thenetwork, (b) selecting a categorical criteria for viewing transactionsfrom one or more interactive menus accessible through the interface, (c)submitting the categorical criteria, the criteria used to calculate andrender the transaction data and (d) viewing the resulting display oftransaction data.

In a preferred embodiment, the method is practiced on the Internetnetwork. In one aspect of the method in step (a), the interactivetransaction-viewing interface is a personalizedhyper-text-markup-language interface served by a portal server connectedto the network. In another aspect of the method in step (a), the remotenode is a personal computer with accessibility to the network. In stillanother aspect in step (a), the remote node is a cellular telephone withaccessibility to the network. In another aspect, the remote node is ahand-held computer with accessibility to the network. In preferredaspects of the method in step (b), the categorical criteria for viewingtransactions include account, timeframe, and by category including foodand beverage, utilities, home, auto, charitable contribution, andentertainment. Also, in one aspect in step (b), an additional option ispresented for ordering a graphic chart according to the selectedcriteria.

Now for the first time an interactive transaction-viewing module isprovided enabling a user to order a multiplicity of transactionalhistory views according to selected criteria wherein all of the optionalviews are attainable through a single interface.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

FIG. 1 is an overview of an Internet portal system and network accordingto an embodiment of the present invention.

FIG. 2 is an exemplary plan view of a personalized portal home pageapplication as it may be seen on a display monitor according to anembodiment of the present invention.

FIG. 3 is a flow diagram illustrating user interaction with the Internetportal of FIG. 1.

FIG. 4 is a block diagram illustrating a summarization software agentand capabilities thereof according to an embodiment of the presentinvention.

FIG. 5 is a logical flow chart illustrating an exemplary summarizationprocess performed by the software agent of FIG. 4 operating in auser-defined mode.

FIG. 6 is a logical flow chart illustrating an exemplary summarizationprocess performed by the software agent of FIG. 4 in a User-independentsmart mode with minimum user input.

FIG. 7 is an overview of a meta-summarization process according to anembodiment of the present invention.

FIG. 8 is a block diagram illustrating components and functions of thedatabase-reporting engine of FIG. 7 according to an embodiment of thepresent invention.

FIG. 9 is a process flow diagram illustrating logical user and systemsteps for initialization to completion of a meta-summarized reportaccording to an embodiment of the present invention.

FIG. 10 is a representative view of an actual screen shot of ameta-summarized report on display in a user's browser interfaceaccording to an embodiment of the present invention.

FIG. 11 is an exemplary screen shot of an interactive interface suitefor enabling multipoint account management capabilities according to anembodiment of the present invention.

FIG. 12 is an exemplary screen shot of a secondary interface invoked asa result of user interaction with module 219 of FIG. 11 according to anembodiment of the present invention.

FIG. 13 is an exemplary screen shot of a secondary interface resultingfrom invocation of transaction center module 221 of FIG. 11 according toan embodiment of the present invention.

FIG. 14 is an exemplary screen shot of a secondary interface resultingfrom invocation of network module 215 of FIG. 11.

FIG. 15 is an exemplary screen shot of a portfolio tracker interfaceresulting from invocation of portfolio tracker module 227 of FIG. 11.

FIG. 16 is an overview of a communications network wherein an Internetportal system is practiced according to an embodiment of the presentinvention

FIG. 17 is an exemplary screen shot of a personalized interactiveinterface suite including a transaction center module according toembodiment of the present invention.

FIG. 18 is an exemplary screen shot of the Transaction Center—Defaultview of FIG. 13 caused to display through interaction with ViewTransactions button 307 of FIG. 17.

FIG. 19 is an exemplary screen shot of a Transaction Center according toan embodiment of the present invention.

FIG. 20 is an exemplary screen shot of the transaction center:transaction history/all accounts interface which is accessed by clickingon the transaction history button 319 of FIG. 18 or FIG. 19.

FIG. 21 is an exemplary view of a screen shot that displays transactionhistory/all accounts—by category: YTD.

FIG. 22 is an exemplary screen shot of a transaction history/bar graphdisplayed as a result of user interaction with chart it icon 333 ofFIGS. 20 and 21.

FIG. 23 is an exemplary screen shot of a transaction history/line graphinterface.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

According to a preferred embodiment of the present invention, a uniqueInternet portal is provided and adapted to provide unique services tousers who have obtained access via an Internet or other networkconnection from an Internet-capable appliance. Such an interfaceprovides users with a method for storing many personal WEB pages andfurther provides search function and certain task-performing functions.The methods and apparatus of the present invention are taught inenabling detail below.

FIG. 1 is an overview of an Internet portal system 11 and Internetnetwork 13 according to an embodiment of the present invention. Portalsystem 11, in this embodiment, operates as an ISP in addition to aunique network portal, but may, in other embodiments be implemented as astand-alone Internet server. In yet other embodiments the service andapparatus described herein may also be provided by such as a search andlisting service (AltaVista™, Yahoo™) or by any other enterprise hostinga WEB-connected server.

Internet 13 is representative of a preferred use of the presentinvention, but should not be considered limiting, as the invention couldapply in other networks and combinations of networks.

ISP 15 in this embodiment comprises a server 31, a modem bank 33,represented here by a single modem, and a mass storage repository 29 forstoring digital data. The modem bank is a convenience, as connection tothe server could be by another type of network link. ISP 15, as istypical in the art, provides Internet access services for individualsubscribers. In addition to well-known Internet access services, ISP 15also provides a unique subscription service as an Internet portal forthe purpose of storing many WEB pages or destinations along with anypasswords and or personal codes associated with those pages, in a mannerdescribed in more detail below. This unique portal service is providedby execution of Portal Software 35, which is termed by the inventors thePassword-All suite. The software of the invention is referred to hereinboth as the Portal Software, and as the Password-all software suite.Also, in much of the description below, the apparatus of the inventionis referred to by the Password-All terminology, such as the Password-AllServer or Password-All Portal.

ISP 15 is connected to Internet 13 as shown. Other equipment known inthe art to be present and connected to a network such as Internet 13,for example, IP data routers, data switches, gateway routers, and thelike, are not illustrated here but may be assumed to be present. Accessto ISP 15 is through a connection-oriented telephone system as is knownin the art, or through any other Internet/WEB access connection, such asthrough a cable modem, special network connection (e.g. T1), ISDN, andso forth. Such connection is illustrated via access line 19 fromInternet appliance 17 through modem bank 33.

In a preferred embodiment a user has access to Internet Password-AllPortal services by a user name and password as is well known in the art,which provides an individualized WEB page to the subscriber. In anotherembodiment wherein a user has other individuals that use his or herInternet account, then an additional password or code unique to the usermay be required before access to portal 31 is granted. Such personalizedPortal WEB pages may be stored in repository 29, which may be anyconvenient form of mass storage.

Three Internet servers 23, 25, and 27, are shown in Internet 13, andrepresent Internet servers hosted by various enterprises and subscribedto by a user operating appliance 17. For example, server 23 may be abank server wherein interactive on-line banking and account managing maybe performed. Server 25 may be an investment server wherein investmentaccounts may be created and managed. Server 27 may be an airline ortravel server wherein flights may be booked, tickets may be purchased,and so on. In this example, all three servers are secure serversrequiring user ID and password for access, but the invention is notnecessarily limited to just secure services.

In a preferred embodiment of the present invention, a subscribing useroperating an Internet-capable appliance, such as appliance 17, connectsto Password-All Portal system 11 hosted by ISP 15, and thereby gainsaccess to a personalized, interactive WEB page, which in turn providesaccess to any one of a number of servers on Internet 13 such as servers23, 25, and 27, without being required to enter additional passwords orcodes. In a preferred embodiment the software that enables this serviceis termed Password-All by the inventors. Password-All may be consideredto be a software suite executing on the unique server, and in someinstances also on the user's station (client). Additional interactivityprovided by portal software 35 allows a connected user to search hislisted pages for information associated with keywords, text strings, orthe like, and allows a user to program user-defined tasks involvingaccess and interaction with one or more Internet-connected servers suchas servers 23, 25, and 27 according to a pre-defined time schedule.These functions are taught in enabling detail below.

FIG. 2 is an illustration of a personalized portal page as may be seenon a display monitor according to an embodiment of the presentinvention, provided by Password-All Portal software 35 executing onserver 31, in response to secure access by a subscriber. Page 32presents an interactive listing 34 of user-subscribed or member WEBpages, identified in this example by URL, but which may also beidentified by any convenient pseudonym, preferably descriptive, alongwith user name and typically encrypted password information for eachpage. Listed in a first column under destination, are exemplarydestinations LBC.com, My Bank.com, My Stocks.com, My shopping.com,Mortgage.com, and Airline.com. These are but a few of many exemplarydestinations that may be present and listed as such on page 33. In orderto view additional listings listed but not immediately viewable fromwithin application 33, a scroll bar 35 is provided and adapted to allowa user to scroll up or down the list to enable viewing as is known inthe art.

Items listed in list 34 in this example may be considered destinationson such as servers 23, 25, and 27 of FIG. 1. Typically the URLassociated with an item on this list will not take a user to a server,per se, but to a page stored on a server. User names and password dataassociated with each item in list 34 are illustrated in respectivecolumns labeled user name, and password, to the right of the columnlabeled destination. Each listing, or at least a portion of eachlisting, is a hyperlink invoking, when selected, the URL to thatdestination. In some instances a particular service may have more thanone associated URL. For example, My Bank.com may have more than one URLassociated for such as different accounts or businesses associated alsowith a single subscriber. In this case there may be a sub-listing fordifferent destinations associated with a single higher-level listing.This expedient is not shown, but given this teaching the mechanism willbe apparent to those with skill in the art.

In some embodiments one page 33 may be shared by more than one user,such as a husband and wife sharing a common account and subscription. Aninstance of this is illustrated herein with respect to the serverlabeled Mortgage.com wherein both a John and a Jane Doe are listedtogether under the column labeled user name. In another embodiment, anetwork of individuals, perhaps business owners, authorized co-workers,investment parties, or the like may share one application. In this way,system 11 may be adapted for private individuals as well as businessuses.

After gaining access to application 33 which is served via Internetportal server 31 of FIG. 1, a user may scroll, highlight, and select anyURL in his or her list 34 for the purpose of navigation to thatparticular destination for further interaction. Application 33 alreadyhas each password and user name listed for each URL. It is notnecessary, however, that the password and user name be displayed for auser or users. These may well be stored transparently in a user'sprofile, and invoked as needed as a user makes selections. Therefore, auser is spared the need of entering passwords and user names for anydestinations enabled by list 34. Of course, each list 34 is built,configured and maintained by a subscribing user or users, and an editingfacility is also provided wherein a user may edit and update listings,including changing URL's adding and deleting listings, and the like.

In another aspect of the invention new listings for a user's profile,such as a new passthrough to a bank or other enterprise page, may beadded semi-automatically as follows: Typically, when a user opens a newaccount with an enterprise through interaction with a WEB page hosted bythe enterprise, the user is required to provide certain information,which will typically include such as the user's ID, address, e-mailaccount, and so forth, and typically a new user name and password toaccess the account. In this process the user will be interacting withthe enterprise's page from his/her browser. A Password-All plug-in isprovided wherein, after entering the required information for the newenterprise, the user may activate a pre-determined signal (right click,key stroke, etc.), and the Password-All suite will then enter a newpassthrough in the user's Password-All profile at the Password-AllPortal server.

In a related method for new entries, the enterprise hosting thePassword-All Portal may, by agreement with other enterprises, providelog-in and sign-up services at the Password-All Portal, with most actiontransparent to the user. For example, there may be, at the Password-AllPortal, a selectable browser list of cooperating enterprises, such asbanks, security services, and the like, and a user having a Password-AllPortal subscription and profile may select among such cooperatingenterprises and open new accounts, which will simultaneously andautomatically be added to the Password-All Portal page for the user andto the server hosted by the cooperating enterprise. There may be someinteractivity required for different accounts, but in the main, muchinformation from the user's profile may be used directly without beingre-entered.

The inventors have anticipated that many potential users may well besuspicious of providing passwords and user names to an enterprisehosting a Password-All Portal Server executing a service likePassword-All according to embodiments of the present invention. Toaccommodate this problem, in preferred embodiments, it is not necessarythat the user provide the cleartext password to Password. All. Instead,an encrypted version of each password is provided. When a user links tohis passthrough page in Password-All at the Password-All Portal server,when he/she invokes a hyperlink, the encrypted password is returned tothe user's system, which then, by virtue of the kept encryption key ormaster password, invokes the true and necessary password for connectionto the selected destination. It is thus not necessary that cleartextpasswords be stored at the Password-All Portal server, where they may bevulnerable to attack from outside sources, or to perceived misuse inother ways as well.

In a related safety measure, in a preferred embodiment of the invention,a user's complete profile is never stored on a single server, but isdistributed over two or more, preferably more, servers, so any problemwith any one server will minimize the overall effect for any particularuser.

Password-All, as described above, allows a user to access a completelist of the user's usual cyberspace destinations, complete withnecessary log-on data, stored in an encrypted fashion, so a user maysimply select a destination (a hyperlink) in the Password-All list, andthe user's browser then invokes the URL for the selected destination. Inan added feature, Password-All may display banner ads and other types ofadvertisement during the navigation time between a hyperlink beinginvoked and the time the destination WEB page is displayed.

In yet another embodiment of the invention, a user/subscriber need notaccess the Password-All page to enjoy the advantages of the uniquefeatures provided. In this variation, a Plug-In is provided for thesubscriber's WEB browser. If the subscriber navigates by use of thelocal browser to a WEB page requiring a secure log-in, such as his/heron-line banking destination, when the subscriber is presented with aninput window for ID and Password, the plug in may be activated by apredetermined user input, such as a hot key or right click of the mousedevice. The plug-in then accesses, transparently, the Password-All page(which may be cached at the client), and automatically accesses andprovides the needed data for log-on.

In yet another aspect of the invention a search option 37 allows a userto search list 34 for specific URL's based on typed input such askeywords or the like. In some cases, the number of URL's stored in list34 can be extensive making a search function such as function 37 anattractive option. A criteria dialog box 51 illustrated as logicallyseparated from and below list 34 is provided and adapted to accept inputfor search option 37 as is known in the art. In one embodiment, searchoption 37 may bring up a second window wherein a dialog box such as box51 could be located.

In another aspect of the invention the search function may also beconfigured in a window invoked from window 33, and caused to search allor selected ones of listed destinations, and to return results in amanner that may be, at least to some extent, configured by a user. Forexample, a dialog box may be presented wherein a user may enter a searchcriteria, and select among all of the listed destinations. The searchwill then access each of the selected destinations in turn, and theresult may be presented to the user as each instance of the criteria isfound, or results may be listed in a manner to be accessed after thesearch.

Preferably the search function is a part of the Password-All Portalsoftware, available for all users, and may be accessed by hyperlinks inuser's personal pages. In some embodiments users may create highlyindividualized search functions that may be stored in a manner to beusable only by the user who creates such a function.

In many aspects of the present invention, knowledge of specific WEBpages, and certain types of WEB pages, is highly desirable. In manyembodiments characteristics of destination WEB pages are researched bypersons (facilitators) maintaining and enhancing Password-All Portalsoftware 35, and many characteristics may be provided in configurationmodules for users to accomplish specific tasks. In most cases thesecharacteristics are invoked and incorporated transparent to the user.

In yet another aspect of the present invention, the Password-All suiteis structured to provide periodic reports to a user, in a manner to bestructured and timed by the user, through the user's profile. Forexample, reports of changes in account balances in bank accounts, stockpurchases, stock values, total airline travel purchases, frequent-fliermiles, and the like may be summarized and provided to the users in manydifferent ways. Because the Password-All Portal server with thePassword-All software site handles a broad variety of transactionaltraffic for a user, there is an opportunity to summarize and collect andprocess statistics in many useful ways. In preferred embodiments of theinvention such reports may be furnished and implemented in a number ofdifferent ways, including being displayed on the user's secure personalWEB page on the Password-All Portal.

In addition to the ability of performing tasks as described above, taskresults including reports, and hard documents such as airline ticketsmay be sent over the Internet or other data packet-networks touser-defined destinations such as fax machines, connected computernodes, e-mail servers, and other Internet-connected appliances. Alltasks may be set-up and caused to run according to user-definedschedules while the user is doing something else or is otherwise notengaged with the scheduled task.

In another embodiment of the present invention, recognizing theincreasing use of the Internet for fiscal transactions, such aspurchasing goods and services, a facility is provided in a user'sprofile to automatically track transactions made at variousdestinations, and to authorize payment either on atransaction-by-transaction basis, or after a session, using access tothe user's bank accounts, all of which may be pre-programmed andauthorized by the user.

Other functions or options illustrated as part of application 35 includea last URL option 41, an update function 43, and an add function 45.Function 41 allows a user to immediately navigate to a last visited URL.Update function 43 provides a means of updating URL's for content andnew address. An add function enables a user to add additional URL's tolist 34. Similarly, function 45 may also provide a means to deleteentries. Other ways to add accounts are described above. It should benoted that the services provided by the unique Password-All Portal inembodiments of the present invention, and by the Password-All softwaresuite are not limited to destinations requiring passwords and usernames. The Password-All Portal and software in many embodiments may alsobe used to manage all of a user's bookmarks, including editing ofbookmarks and the like. In this aspect, bookmarks will typically bepresented in indexed, grouped, and hierarchical ways.

There are editing features provided with Password-All for adding,acquiring, deleting, and otherwise managing bookmarks. As a convenience,in many embodiments of the invention, bookmarks may be downloaded from auser's Password-All site, and loaded onto the same user's local browser.In this manner, additions and improvements in the bookmark set for auser may be used without the necessity of going to Password-All.Further, bookmarks may be uploaded from a user's local PC to his/herhome page on the Password-All site by use of one or more Password-Allplug-ins.

It will be apparent to the skilled artisan, given the teaching herein,that the functionality provided in various embodiments of the inventionis especially applicable to Internet-capable appliances that may belimited in input capability. For example, a set-top box in a WEB TVapplication may well be without a keyboard for entering IDs andPasswords and the like. In practice of the present invention keyboardentry is minimized or eliminated. The same comments apply to many othersorts of Internet appliances.

In preferred embodiments of the invention, once a subscriber-user is inPassword-All, only an ability to point-and-click is needed for allnavigation. To get into the Password-All site, using a limitedapparatus, such as an appliance without a keyboard or keypad, aSmartcard or embedded password may be used, or some other type ofauthentication.

It will be apparent to one with skill in the art that an interactiveapplication such as application 33 may be provided in a form other thana WEB page without departing from the spirit and scope of the presentinvention. For example, an application such as application 33 may beprovided as a downloadable module or program that may be set-up andconfigured off-line and made operational when on-line.

FIG. 3 is a flow diagram illustrating user interaction with the InternetPassword-All Portal of FIG. 1. The following process steps illustrated,according to an embodiment of the present invention, are intended toillustrate exemplary user-steps and automated software processes thatmay be initiated and invoked during interaction with an Internet portalof the present invention such as portal 31 of FIG. 1. In step 53 a userconnects to the Internet or another previously described switched-packetnetwork via a compatible appliance such as Internet appliance 17 of FIG.1.

At step 55, a user enters a user-name and password, which, in oneembodiment, may simply be his ISP user name and password. In anotherembodiment, a second password or code would be required to access anInternet portal such as portal server 31 of FIG. 1 after logging ontothe Internet through the ISP. In some cases, having a specialarrangement with the ISP, there may be one password for both Internetaccess through the ISP and for Password-All. At step 57 a personal WEBpage such as page 32 of FIG. 2 is displayed via Internet portal server31. At minimum, the personalized WEB page will contain all userconfigured URL's, and may also be enhanced by a search function, amongother possibilities.

In step 58 a user will, minimally, select a URL from his or herbookmarked destinations, and as is known by hyperlink technology, thetransparent URL will be invoked, and the user will navigate to thatdestination for the purpose of normal user interaction. In this action,the Password-All Portal software transparently logs the user on to thedestination page, if such log-on is needed.

At step 60 the user invokes a search engine by clicking on an optionsuch as described option 37 of FIG. 2. At step 62, the user inputssearch parameters into a provided text field such as text field 51 ofFIG. 2. After inputting such parameters, the user starts the search by abutton such as button 52. The search engine extracts information in step64. Such information may be, in one option, of the form of URL's fittingthe description provided by search parameters. A searched list of URL'smay be presented in a separate generated page in step 66 after which auser may select which URL to navigate to. In an optional searchfunction, the user may provide search criteria, and search any or all ofthe possible destinations for the criteria.

In another embodiment wherein WEB pages are cached in their presentableform, information extracted in step 64 may include any informationcontained in any of the stored pages such as text, pictures, interactivecontent, or the like. In this case, one displayed result page mayprovide generated links to search results that include the URLassociated with the results. Perhaps by clicking on a text or graphicresult, the associated WEB page will be displayed for the user with theresult highlighted and in view with regards to the display window.

Enhanced Agent for WEB Summaries

In another aspect of the present invention, a software agent, termed agatherer by the inventors, is adapted to gather and return summaryinformation about URL's according to user request or enterprisediscretion. This is accomplished in embodiments of the present inventionby a unique scripting and language parsing method provided by theinventor wherein human knowledge workers associated with the serviceprovide written scripts to such a gatherer according to subscriber orenterprise directives. Such a software gatherer, and capabilitiesthereof, is described in enabling detail below.

Referring now to FIG. 1, there is illustrated an exemplary architecturerepresenting a portal service-network which, in this case is hosted byISP 15. Portal software 35 in this embodiment executes on portal server31 set-up at the ISP location. Mass repository 29 is used for storingsubscriber information such as passwords, login names, and the like.Internet servers 23, 25, and 27 represent servers that are adapted toserve WEB pages of enterprises patronized by a subscriber to the portalservice such as one operating Internet appliance 17.

The main purpose of portal software 35 as described above with referenceto FIG. 2, is to provide an interactive application that lists all ofthe subscriber's WEB sites in the form of hyperlinks. When a userinvokes a hyperlink from his personal list, software 35 uses thesubscriber's personal information to provide an automatic andtransparent login function for the subscriber while jumping thesubscriber to the subject destination.

Referring again to FIG. 2, an interactive list 34 containinguser-entered hyperlinks and a set of interactive tools is displayed to asubscriber by portal software 35 of FIG. 1. One of the tools availableto a subscriber interacting with list 34 is agent (software) 39. Agent39 may be programmed to perform certain tasks such as obtaining accountinformation, executing simple transactions, returning user-requestednotification information about upcoming events, and so on. Searchfunction 37 and update function 43 may be integrated with agent 39 asrequired to aid in functionality.

It is described in the above disclosure that agent 39 may, in someembodiments, search for and return certain summary information containedon user-subscribed WEB pages, such as account summaries, order trackinginformation and certain other information according to user-definedparameters. This feature may be programmed by a user to work on aperiodic time schedule, or on demand.

In the following disclosure, enhancements are provided to agent 39. Suchenhancements, described in detail below, may be integrated into agent 39of portal software 35 (FIGS. 1 and 2); and may be provided as a separateagent or gatherer to run with portal software 35; or may, in someembodiments, be provided as a standalone service that is separate fromportal software 35.

FIG. 4 is a block diagram illustrating a summarization software agent 67and various capabilities and layers thereof according to an embodimentof the present invention. Summarization agent 67, hereinafter termedgatherer 67, is a programmable and interactive software applicationadapted to run on a network server. Gatherer 67 may, in one embodiment,be integrated with portal software 35 of FIG. 1 and be provided in theform of a software module separate from agent 39 (FIG. 2). In anotherembodiment, gatherer 67 may be a part of agent 39 as an enhancement tothe function of that agent as previously described. In still anotherembodiment, gatherer 67 may be provided as a parent or client-sideapplication controlled by a separate service from the portal servicedescribed above.

In this exemplary embodiment gatherer 67 is a multi-featured softwareapplication having a variety of sub-modules and interface modulesincorporated therein to provide enhanced function. Gatherer 67 has aclient/service interface layer 69 adapted to enable directive input fromboth a client (user) and a knowledge worker or workers associated withthe service. A browser interface 77 is provided in layer 69, and adaptedto provide access to application 67 from a browser running on a client'sPC or other Internet or network appliance. Interface 77 facilitatesbi-directional communication with a user's browser application (notshown) for the purpose of allowing the user to input summary requestsinto gatherer 67 and receive summary results. Interface 77 supports allexisting network communication protocols such as may be known in theart, and may be adapted to support future protocols.

Layer 69 also comprises a unique input scripting module 79 that isadapted to allow a human knowledge worker to create and supply directivescripts containing the site logic needed by gatherer 67 to find andretrieve data from a WEB site. In this case, gatherer 67 executes andruns on a network server such as server 31 of FIG. 1. However, this isnot required in order to practice the present invention.

It is assumed in this example that gatherer 67 is part of the portalsoftware suite 35 running on server 31 of FIG. 1. Gatherer 67 may beprovided as several dedicated agents, or as one multi-functional agentwithout departing from the spirit and scope of the present invention.For example, one gatherer 67 may be scripted and programmed to execute asingle user request with additional gatherers 67 called upon to performadditional user-requests. Alternatively, one gatherer 67 may bededicated and assigned to each individual user and adapted to handle allrequests from that user.

Interface layer 69 facilitates exchange of information from both aclient and a knowledge worker. A client operating a WEB browser with anappropriate plug-in is enabled to communicate and interact with gatherer67. For example, a user may enter a request to return a summary ofpricing for all apartments renting for under $1000.00 per month locatedin a given area (defined by the user) from apartments.com (one of user'sregistered WEB sites). The just mentioned request would be categorizedas either a periodic request, or a one time (on demand) request. Thecommunicated request initiates a service action wherein a knowledgeworker associated with the service uses module 79 to set-up gatherer 67to perform its function. Module 79 is typically executed from anetwork-connected PC operated by the knowledge worker.

According to an embodiment of the present invention, a unique scriptingmethod facilitated by module 79 is provided to enable gatherer 67 toobtain the goal information requested by a user. For example, the abovementioned example of WEB-site apartments.com has a specific HTML(hyper-text-markup-language) logic that it uses to create its site andpost its information. Such site logic is relatively standard fare for amajority of different sites hosted by different entities. Using thisknowledge, a knowledge worker creates a site-specific script or templatefor gatherer 67 to follow. Such a template contains descriptions andlocations of the appropriate fields used, for example, atapartments.com. Apartment description, location, deposit information,rental information, agent contact information, and other related fieldsare matched in terms of location and label description on the templatecreated with module 79. Completed templates are stored in a databasecontained in a storage facility such as, perhaps, repository 29 ofFIG. 1. Such templates may be reused and may be updated (edited) withnew data.

In one embodiment, one script may contain site logics for a plurality ofWEB pages, and instructions for specific navigational instruction andpassword or login information may be contained therein and executedserially, such as one site at a time. It is important to note that theknowledge worker or workers may perform much of their scripting viaautomatic controls such as by object linking and embedding (OLE) and aminor portion of scripting may be performed manually in an appropriatecomputer language, many of which are known in the art).

Gatherer 67 also has a process layer 71 adapted for internal informationgathering and parameter configuration. An optional portal serverinterface 81 is provided and adapted to allow gather 67 to provideupdated information to a user's list of hyperlinks and also to obtaindata from portal server 31 if required. For example, required hyperlinksmay be mirrored from a user's home page to a scripting template fornavigational purposes. In an embodiment wherein gatherer 67 is part of astandalone service, a convention for providing user login informationmay be supplied at the client's end when a request is made. For example,an encrypted password may be supplied by a client plug-in and gatherer67 may temporarily borrow the user's encryption key when auto login isperformed.

An appliance configuration module 83 is provided and adapted to allow auser to define and configure an Internet appliance to communicate withthe service and receive summary information. Such appliances may includebut are not limited to palm top PC's, lap top PC's, cellular telephones,WEB TV's, and so on. Typically, a user will be presented a configurationWEB page from a network server that displays in his browser window onhis desktop PC. The page contains an interface for communicating deviceparameters and communication protocol types to module 83. In this way, auser may configure a preferred device for receipt of summaryinformation. Device parameters and communication protocols inherent tosuch a device are incorporated into the scripting of the site templateand are used as instructions for WEB summary delivery.

A navigation layer 73 is provided and adapted to perform the function ofexternal site navigation and data gathering for gatherer 67. To thisend, a communication interface/browser control module 85 is provided andadapted to function as a WEB browser to access WEB sites containing WEBdata. Control 85 receives its instruction from the scripted templatecreated by the knowledge worker.

A parsing engine 87 is provided and adapted to parse individual WEBsites according to a template created via scripting module 79. Parsingengine 87 may be a Pearl engine, an IE HTML engine, or any other orcombination of known parsing engines. The template (not shown) tellscontrol 85 and parsing engine 87 where to go and what fields at thedestination site to look for to access desired data. Once the datafields are located, parsing engine 87 gathers current data in theappropriate field, and returns that data to the service for furtherprocessing such as data conversion, compression and storage, and thelike.

Because WEB sites use tools that use consistent logic in setting uptheir sites, this logic may be used by the summarization service toinstruct control 83 and parsing engine 87. The inventor provides hereinan exemplary script logic for navigating to and garnishing data fromamazon™.com. The hyperlinks and/or actual URLs required for navigationare not shown, but may be assumed to be included in the template script.In this example, a company name Yodlee (known to the inventors) is usedin the script for naming object holders and object containers, which arein this case Active X™ conventions. In another embodiment, Java™ scriptor another object linking control may be used. The scripted templatelogic example is as follows:

# Site amazon.orders.x - shows status of orders from Amazon login( 7 );get( “/exec/obidos/order-list/” ); my @tables =get_tables_containing_text( “Orders:” ); my $order_list = newYodlee::ObjectHolder( ‘orders’ ); $order_list->source( ‘amazon’ );$order_list->link_info( get_link_info( ) ); my @href_list; my@container_list; foreach my $table ( @tables ) {   my @rows =get_table_rows( ); foreach my $i ( 0 .. $#rows ) {   select_row( $i );my $text = get_text( $rows[ $i ] ); next if $text =~ /Orders:|Status/;my @items = get_row_items( ); next unless @items >= 4; my( $order_num,$date, $status ); select_cell( 1 ); $order_num = get_cell_text( ); my$href = get_url_of_first_href( get_cell( ) ); select_cell( 2 ); $date =get_cell_text( ); select_cell( 3 ); $status = get_cell_text( ); nextunless defined $order_num and defined $date and defined $status; my$order = new Yodlee::Container( ‘orders’ ); $order->order_number($order_num ); $order->date( $date ); $order->status( $status );$order_list->push_object( $order ); if( defined $href ) {  push(@href_list, $href );  push( @container_list, $order ); foreach my $i ( 0.. $#href_list ) {    get( $href_list[ $i ] );    @tables =get_tables_containing_text( “Items Ordered:” ); foreach my $table (@tables ) {    my @rows = get_table_rows( ); foreach my $j ( 0 .. $#rows) {    select_row( $j );    my $href = get_url_of_first_href( get_row( ));    next unless defined $href;    my @child_list = get_children(get_row( ), ‘a’ );    next unless defined $child_list[ 0 ];    my $text= get_text( $child_list[ 0 ] );    $container_list[ $i ]->description($text );   }  } } result( $order_list );

The above example is a script that instructs control 85 and parser 87 tonavigate to and obtain data from Amazon™.com, specifically that datathat reflects the user's current order status. Scripts may also bewritten to obtain virtually any type of text information available fromany site. For example, a user may wish to obtain the New York Timesheadlines, the top ten performing stocks, a comparative list of flightsfrom San Francisco to New York, etc. In one embodiment, metadata may beassociated with and used in-place of the actual scripted language forthe purpose of reducing complication in the case of many scripts on onetemplate.

A data processing layer 75 is provided and adapted to store, process,and present returned data to users according to enterprise rules andclient direction. A database interface module 89 is provided and adaptedto provide access for gatherer 67 to a mass repository such asrepository 29 of FIG. 1, for the purpose of storing and retrievingsummary data, templates, presentation directives, and so on. Gathereragent 67 may also access data through interface 89 such as profileinformation, user account and URL information, stored site logics and soon. Data scanned from the WEB is stored in a canonical format in adatabase such as repository 29, or in another connected storagefacility. All stored data is, of course, associated with an individualwho requested it, or for whom the data is made available according toenterprise discretion.

A summarization page module 91 is provided and adapted to organize andserve a WEB summary page to a user. Module 91, in some embodiments, mayimmediately push a WEB summary to a user, or module 91 may store suchsummarized pages for a user to access via a pull method, in which case anotification may be sent to the user alerting him of the summary pageavailability. Summarization module 91 includes an HTML renderer that isable to format data into HTML format for WEB page display. In this way,e-mail messages and the like may be presented as HTML text on a user'ssummarization page. Moreover, any summary data from any site may includean embedded hyperlink to that site. In this way, a user looking at ane-mail text in HTML may click on it and launch the appropriate e-mailprogram. Other sites will, by default, be linked through the summarypage.

Many users will access their summary data through a WEB page asdescribed above, however, this is not required in order to practice thepresent invention. In some embodiments, users will want their summaryinformation formatted and delivered to one of a variety ofInternet-capable appliances such as a palm top or, perhaps a cell phone.To this end, the renderer is capable of formatting and presenting thesummary data into a number of formats specific to alternative devices.Examples of different known formats include, but are not limited to XML,plain text, VoxML, HDML, audio, video, and so on.

In a preferred embodiment of the present invention, gather 67 isflexible in such a way as it may act according to enterprise rules,client directives, or a combination of the two. For example, if a usermakes a request for summary data about a user/subscribed WEB page to beperiodically executed and presented in the form of a HTML document, thengather 67 would automatically access and analyze the required internalinformation and user provided information to formulate a directive.Using scripting module 79, a knowledge worker provides a template (ifone is not already created for that site) that contains the “where togo” and “what to get” information according to site logic, user input,and known information.

Alternatively, if a user requests a summary about data on one of hissites such as, perhaps, current interest rates and re-finance costs athis mortgage site, the service may at its own discretion provide anadditional unsolicited summary from an alternate mortgage site forcomparison. This type of summarization would be designed to enhance auser's position based on his profile information. In this case, updateddata about latest interest rates, stock performances, car prices,airline ticket discounts, and so on would be stored by the service forcomparative purposes. If a user request for a summary can be equaled orbettered in terms of any advantage to the user, such summary data may beincluded.

In many cases, created templates may be re-used unless a WEB sitechanges it's site logic parameters, in which case, the new logic must beaccessed and any existing templates must be updated, or a new templatemay be created for the site. The templates contain site-specific scriptobtained from the site and stored by the knowledge workers. In oneembodiment, companies hosting WEB pages automatically provide their sitelogics and any logic updates to the service by virtue of an agreementbetween the service and the WEB hosts.

In an alternative embodiment gatherer 67 may be implemented as a clientapplication installed on a user's PC. In this embodiment, a user wouldnot be required to supply log-in or password codes. Summarizationscripts may be sent to the client software and templates may beautomatically created with the appropriate scripts using log-in andpassword information encrypted and stored locally on the user's machine.

In addition to providing WEB summary information, gatherer 67 may alsobe used to provide such as automatic registration to new sites, and forupdating old registration information to existing sites. For example, ifa user wishes to subscribe, or register at a new site, only theidentification of the site is required from the user as long as hispertinate information has not changed. If a new password or the like isrequired, gatherer 67 through control module 73 may present login orpassword codes from a list of alternative codes provided by a user. Inanother embodiment, a database (not shown) containing a wealth ofpassword options may be accessed by gatherer 67 for the purpose oftrying different passwords until one is accepted by the site. Once apassword or log-in code is accepted, it may be sent to a user and storedin his password list and at the network level.

It will be apparent to one with skill in the art that a softwareapplication such as gatherer 67 may be implemented in many separatelocations connected in a data network. For example, a plurality ofgatherer applications may be distributed over many separate serverslinked to one or more mass repositories. Client applications include butare not limited to a WEB-browser plug-in for communicating to theservice. Plug-in extensions may also be afforded to proxy servers sothat auto-login and data access may still be performed transparent to auser.

In another embodiment, plug-ins enabling communication with gatherer 67may be provided and configured to run on other network devices for thepurpose of enabling such a device to initiate a request and get aresponse without the need for a desktop computer.

In most embodiments a user operating a desktop PC will order a one timeor periodic summary related to some or all of his subscribed WEB sites.A logical flow of an exemplary request/response interaction is providedbelow.

FIG. 5 is a logical flow chart illustrating an exemplary summarizationprocess performed by the software agent of FIG. 4 operating in auser-defined mode. In step 93, a user has initiated a new request for asummary (summary order). It is assumed for the purpose of discussion,that the request of step 93 involves a site wherein no template has beencreated. In step 95, the request is received and analyzed. A knowledgeworker will likely perform this step. The new request may be posted tothe user's portal home page, sent directly to gatherer 67, or evencommunicated through e-mail or other media to the service.

In step 97 a knowledge worker accesses particular site logic associatedwith the request URLs. For example, if the request involves a pluralityof URLs, then all site logics for those URLs are accessed. Logic may beavailable in a repository such as repository 29 of FIG. 1 if they wereobtained at the time of user registration to a particular URL, or sentin by WEB-site hosts shortly after registration. If it is a completelynew URL, then the logic must be obtained from the site. In most caseshowever, the logic will be known by virtue of a plurality of usersaccessing common URLs. Therefore cross-linking in a database oflogic/user associations may be performed to access a logic for a sitethat is new to one particular user, but not new to another.

In step 99, the knowledge worker creates a template by virtue ofscripting module 79 (FIG. 4) containing all site logic, URLs, log-in andpassword information, and the user request information. As describedpreviously, templates may be re-used for a same request. In most cases,scripting may be mostly automated with minimum manual input performed bythe knowledge worker. In many cases, an existing template will match anew request exactly, and may be re-used. In that case steps 97, 99, and101 would not be required.

In step 101 the template is stored and associated with the requestinguser. The stored template may now be retrieved at a scheduled time forperforming the summary gathering. At step 103, a browser control such asmodule 85 of FIG. 4 is activated to access the stored template andnavigate to specified URLs for the purpose of gathering summary data. Ifa timing function is attributed to the template stored in step 101, thenthe template may self execute and call up the browser function. Inanother embodiment, the knowledge worker may notify the browser controlto get the template for its next task. In some embodiments, a pluralityof controls may be used with one template as previously described.

In step 105, automatic log-in is performed, if required, to gain accessto each specified URL. In step 107, a specified WEB-page is navigated toand parsed for requested data according to the logic on the template. Ifthere are a plurality of WEB-pages to parse, then this step is repeatedfor the number of pages. A variety of parsing engines may be used forthis process such as an IE™ parser, or a Pearl™ parser. Only therequested data is kept in step 107.

A request may be an on-demand request requiring immediate return, or ascheduled request wherein data may be posted. At step 109, such logic isconfirmed. If the data is to be presented according to a periodicschedule, then summary data parsed in step 107 is stored for later usein step 111. In step 113, the summary data is rendered as HTML if notalready formatted, and displayed in the form of a summary WEB-page instep 115. The summary page may be posted for access by a user at a timeconvenient to the user (pull), or may be pushed as a WEB-page to theuser and be made to automatically display on the user's PC. Notificationof summary page availability may also be sent to a user to alert him ofcompletion of order.

If the summary data is from a one-time on-demand request and requiredimmediately by a user, then a network appliance and data delivery method(configured by the user) is confirmed, and the data is rendered in theappropriate format for delivery and display in step 117. In step 119,the summary data is delivered according to protocol to a user'sdesignated appliance. In step 121 a user receives requested informationin the appropriate format.

It will be apparent to one with skill in the art that there may be moreor fewer logical steps as well as added sub-steps than are illustratedin this example. For example, step 105 may in other embodiments includesub-steps such as getting an encryption key from a user. In stillanother embodiment, part of a request may be rendered as HTML as in step113 while certain other portions of the same request data might berendered in another format and delivered via alternative methods. Thereare many possibilities.

The method and apparatus of the present invention may be used to presentsummaries to users without user input. Process logic such as this isdetailed below.

FIG. 6 is a logical flow chart illustrating an exemplary summarizationprocess performed by the software agent of FIG. 4 in a User-independentsmart mode with minimum or no user input. In step 117 anenterprise-initiated summary process begins. In this case, theenterprise may be assisting a user in finding a better deal or, perhapspresenting the individual with summaries from and links to alternativepages not yet subscribed to by a user.

In step 119, a database containing user information and parameters isaccessed and reviewed. Certain information specific to a user may berequired to initiate an enterprise-sponsored summary report. At step121, the knowledge worker accesses the site logic specific to thespecified target site or sites for summarization. In step 123, theknowledge worker modifies an existing user template, or creates a newone if necessary. At step 125 the template is stored in a repositorysuch as repository 29 and associated with the user.

As described in FIG. 5, the template either self-executes according to atimed function and invokes a browser control such as control 85 (FIG.4), or is accessed by control 85 as a result of task notification. Instep 127, the browser control begins navigation. Auto logins areperformed, if required, in step 129 to gain access to selected sites. Ifthe WEB pages are new to a user, and the user has no registration withthe WEB site, then through agreement, or other convention, the servicemay be provided access to such sites. Such an agreement may be made, forexample, if the host of the WEB site realizes a possibility of gaining anew customer if the customer likes the summary information presented. Inmany other situations, no password or login information is required toobtain general information that is not personal to a client.

In step 131, all sites are parsed for summary data and stored incanonical fashion in step 133. At step 135, the data is compiled andrendered as HTML for presentation on a summary page. In step 137, a WEBsummary containing all of the data is made available to a user and theuser is notified of its existence.

Providing certain information not requested by a user may aid inenhancing a user's organization of is current business on the WEB.Moreover, unsolicited WEB summaries may provide better opportunitiesthan the current options in the user's profile. Of course, assisting auser in this manner will require that the enterprise (service) haveaccess to the user's profile and existing account and serviceinformation with various WEB sites on the user's list. A user may forbiduse of a user's personal information, in which case, noenterprise-initiated summaries would be performed unless they areconducted strictly in an offer mode instead of a comparative mode.

The method and apparatus also may be practiced in a language andplatform independent manner, and be implemented over a variety ofscalable server architectures.

Presenting Meta-Summarized Reports

In another aspect of the present invention, a method is provided largelythrough unique software wherein summary reports may be ordered andpresented to users, the reports reflecting calculated andsolution-orientated results. This type of summarizing is termedmeta-summarization by the inventors, because it is a summarization overa plurality of data sources. Such a method is described in enablingdetail below.

FIG. 7 is an overview of a meta-summarization process according to anembodiment of the present invention. The term “meta-summary” is used bythe inventor in this embodiment also to distinguish the meta-summaryprocess taught herein from the summary process taught above in thisspecification; in that meta-summarizing involves interpreting andcalculating data for reporting a solution-orientated result derived fromdata retrieved from multiple network sources.

In this embodiment, a portal station 151 is provided and adapted byvirtue of software and hardware, to perform WEB-summary and presentationservices according to embodiments described in the co-patentapplications listed above. Station 151 may be an ISP, a main Internetserver, or other network connected server or interface station. In thisexample, portal station 151 is continuously connected to a sourcenetwork, which is in this embodiment, the Internet network representedby Internet cloud 139. The above-described network connection isafforded by an Internet-connection line 149 from station 151 to anInternet backbone 147. Internet backbone 147 represents all lines andconnections, including sub-nets that make up a global Internet 139.

Portal station 151 has a means provided therein for maintaining a portalinterface 153. Portal interface 153 is a file-server interface in thisexample, however in other embodiments, differing types ofnetwork-interface hardware may be substituted therefor. Interface 153provides hyper-text-transfer protocol (HTTP) pages over anInternet-connection such as path 161 to subscribing users operating suchas an illustrated network-adapted PC 163. A user operating PC 163 may goon-line, in this case by such as a dial-up connection, and communicatewith portal interface 153 over connection path 161. Connection path 161may be a normal telephone line, an ISDN line, or another known type ofInternet-connection link including wireless connection. A dial-upconnection is illustrated herein only as a more common connectionmethod.

A data repository 157 is provided within station 151 and adapted towarehouse aggregated data on behalf of and about a user. Data repository157 may be part of the same hardware supporting portal interface 153 orit may be a separate hardware implementation connected by a data link.Repository 157 may be of the form of optical storage, or any other knownimplementation used for storing large amounts of digital data.Repository 157 may be assumed to support varied database programs as maybe required to manipulate and organize data or metadata stored therein.

A data gathering sub-system GSS 159 is provided within station 151 andis adapted as a software and hardware implementation capable ofnavigating data-packet networks, such as Internet 139, upon instruction.GSS 159 represents automated browser control/navigation as described inco-pending patent application Ser. No. 09/523,598. GSS 159 is analogousto navigation layer 73 described in FIG. 4 above.

A plurality of network-connected data sources represented herein byfile/data servers 141-145 are illustrated in Internet 139. Servers141-145 are user-subscribed servers known to portal station 151. Forexample, servers 141-145 may represent one user's collectiveWEB-services for banking and investment. Such options include banking,stock trading, retirement account servers, insurance servers, and so on.It is noted here that servers 141-145 are assumed to represent separateWEB-based services subscribed to by one user and are not affiliated withone another. For example, a user operating such as PC 163 would do allof his on-line banking, trading, and investing using servers 141-145 inthis example.

In another embodiment, servers 141-145 may represent all of a user'sfrequented on-line shopping services. The fact that all of servers141-145 are topically related but not affiliated with one another inthis example serves only to aid in explanation of the present inventionas will be seen below.

It is taught in the co-pending patent application entitled “Method andApparatus for Obtaining and Presenting WEB Summaries to Users” that sitenavigation, parsing data, and returning data to users or storage isenabled, in part, by site-logic templates provided typically byknowledge workers. This aspect is represented herein by a PC 167 adaptedfor a knowledge worker (KW). A KW working from a station such as PC 167provides site-logic scripts for navigation to data requested by a userand stored in any one of or all of servers 141-145. Such scripts areprovided to GSS 159 over a data link 165. Summary data stored in such asrepository 157 is stored for user access. In some cases wherein a userrequests immediate data return, data is sent directly to such as portalinterface 153 where a user may then access the data immediately.

According to an embodiment of the present invention, a noveldatabase-reporting engine DBRE 155 is provided and adapted to performformulative processes to aggregated data on behalf of a user. DBRE 155is in itself a database utility and is in a preferred embodiment a partof the software environment of repository 157. In another embodimentDBRE 155 may be part of the software environment of portal interface153.

In this embodiment, DBRE 155 acts as a first “gathering agent” andchecks repository 157 first for user requested data upon request.User-history records of all user transactions at all of his registeredWEB-based services are preferably maintained in repository 157 and areaccessible to DBRE 155. In some cases, services such as thoserepresented by servers 141-145 may provided complete transactionhistories that may be obtained and stored in repository 157 and updatedperiodically. In some cases however, such services may not retainhistory records for users. In this case, a user accessing such servicesthrough his or her portal interface 153 may track each transaction overa normal course of time resulting in a history record for transactionsat that service that is maintained in repository 157.

In the case of servers 141-145, each contains some form of financialportfolio data connected to one user. For example, server 141 mayrepresent a banking service where a user has a savings account. Server142 may represent a banking service where the user has a checkingaccount. Server 143 may represent an on-line investment companymaintaining a fast-changing portfolio of investments and losses for theparticular user. Server 144 may represent a banking company where theuser has an individual retirement account (IRA). Server 145 mayrepresent a mortgage company holding data about the users propertyportfolios. Each site presumably holds current account-statusinformation and a financial history of transactions performed by aparticular user.

To illustrate, assume that all financial data particular to one user isprovided by or obtained from servers 141-145, aggregated in datarepository 157, and updated periodically. A user operating PC 163 mayaccess portal interface 153 by way of Internet connection 161 andrequest a specific result that involves some or all of the data acrossmultiple servers 141-145. One example would be a user-initiated command“calculate my current net-worth”. The resulting meta-summarized reportwould inform a user of his or her calculated net-worth with allfinancial data from all financial data-sources (servers 141-145)analyzed in the process of answering the user query.

In this case DBRE 155 utilizes only data that is already aggregated inrepository 157. Therefore, it is not specifically required that GSS 159navigate on behalf of the user in a case where data held in aggregationis current and sufficient to satisfy a user request. However, if auser's particular request, such as the one stated in the above example,requires navigation to one or more of servers 141-145, GSS 159, usingsite logic provided by KW 167, would navigate to each required site andretrieve the required data. After the required data is aggregated inrepository 157, DBRE 155 may analyze the aggregated data and generate anaccurate report from the aggregated data based on a user's request.

It will be apparent to one with skill in the art that providing a uniqueengine such as DBRE 155 on a user-side of repository 157 saves preciousbandwidth resource required by individual site navigation and return ofdata ordered by a user. Added storage space is required in repository157 for the purpose of storing complete activity histories from multipleWEB services on behalf of users. However, adding such resource andsaving bandwidth represents an intelligent implementation in light ofthe many techniques known in the art for compressing and archiving data.More detail about the function of DBRE 155 is presented below.

FIG. 8 is a block diagram illustrating additional detail, components andfunctions of DBRE 155 of FIG. 7 according to an embodiment of thepresent invention. DBRE 155 is a functional interface capable ofobtaining, analyzing, and preparing data for presentation to a user. Assuch, it contains certain sub-modules responsible for performing certainrequired functions. For example, a control-logic module 171 is providedas part of DBRE 155 and adapted to parse and confirm a user's request aswell as to insure that a user-selected presentation format is availableand appropriate for the type of data result requested by a user. Suchoptions are contained in an options database 173 illustrated asconnected to control module 171 by a double arrow representingbi-directional communication.

Options database 173 may be part of DBRE 155 as illustrated herein, orpart of repository 157 and made accessible to DBRE 155. In the case ofDBRE 155 maintaining its own databases such as options database 173, anda previously described database containing user histories acrossmultiple accounts, then DBRE 155 would be resident in a machine havingenough storage memory to hold all required data. Such a machine could bea processor/server. In another embodiment, all stored data is held inrepository 157.

DBRE 155 also has a runtime engine 177, which performs data analyzingand calculation in order to form specific data results or solutions forusers based on user request. Engine 177 has access to all of themathematical tools and system knowledge required to perform itsobjectives which can vary considerably. A knowledge base (not shown) maybe used as a source of intelligence for engine 177 as is generally knownin the art of configuration models.

Engine 177 performs a wide variety of mathematical functions includingsuch as statistical analysis, summing, averaging, and so on. In oneembodiment, algebraic, geometric, and trigonometric functions are alsoprovided for performing more complex calculations. In most caseshowever, user requests will be geared more toward averaging, summing,predicting probabilities, deriving percentages, and so on. For example,summing multiple bank balances would be a common task. Analyzing on-linespending trends across multiple on-line shopping services would beanother example of a common task. A more complicated report mightcompare shopping trends with income potential and produce a ratio figurealong with recommended ways to improve on the ratio without sacrificingneeded goods. There are many possibilities.

A graphics user interface (GUI) module 181 is provided within DBRE 155and adapted to prepare data according to requested format and arequesting display type. GUI module 181 has knowledge of whichpresentation option was selected from options database 173, andknowledge of the parameters (hardware and software platform) of aparticular device or station that will receive a report. It is notrequired that a report be directed back to an originating device. Insome embodiments, a user may direct a meta-summary report to alternativereceiving devices over different mediums. This assumes, of course, thatthe receiving devices and data networks are known to the system.

In practice of the present invention, a user initiates a requestillustrated herein as an arrow labeled input to a pre-configured request169 from such as his or her browser interface. Request 169 is parsed formeaning in control-logic module 171. If there is an error detected inthe original request 169, such as missing information or an optionselection that is not available, then an error report is immediatelysent back to that user as illustrated by the arrow labeled error report.Control-logic module 171 may check options database 173 to determine ifan unavailable option was selected and present an alternative availableoption back with the error report.

Once module 171 has confirmed a request and confirmed a presentationoption, it accesses a guard (GI) 175 resident on the client side of suchas repository 157 of FIG. 7 to see if there is enough current datastored therein to enable formulation of a valid result. Data obtainedfrom repository 157 of FIG. 1 by way of database interaction is includedin guard 175 and passed to engine 177 for processing. If however, arequired portion of data is missing from repository 155, GSS 159 of FIG.7 may be invoked to retrieve the requested data. An error message may,in this case, be sent back to a user informing him of a requirement tonavigate for a portion of required data.

All of the data required to return a requested report is funneled intoruntime engine 177. All of the appropriate calculations are performedand the resulting data illustrated herein as raw data-results 177 ispassed into GUI module 181. GUI module 181 then prepares the result datafor presentation to a user illustrated herein as an arrow labeledoutput.

As described above, a report may be very simple or quite complex,including text and graphical elements as well. In one embodiment, all ofthe process steps performed on included data may be broken down andreported to a user along with a final result. Presentation options mayinclude spreadsheets, graphs, text reports, pie charts, and so on.

In the example presented above, DBRE 155 is a multi-functional modulethat may be broken down into cooperating sub-modules. However, this isnot required to practice the present invention. One with skill in theart will recognize that there are other orders of modules anddistribution paths that may be utilized to accomplish the same function.For example, DBRE 155 (FIG. 7) may interface directly with GSS 159 (FIG.7) instead of being enhanced for gathering from aggregated data. In thiscase GSS 159 would first check repository 157 before determining ifnavigation is required. In another embodiment navigation may be requiredby default to insure that all data in aggregation is current. There aremany possibilities.

FIG. 9 is a process flow diagram illustrating logical user and systemsteps from initialization to completion of a meta-summarized reportaccording to an embodiment of the present invention. At step 183, a userinitiates a meta-summary report request from such as PC 163 of FIG. 7using a browser/portal interface. A request might be to sum all of myinterest earnings from all of my interest bearing accounts over a 1-yearperiod and return a monthly average. In a preferred embodiment such arequest may be made in a “natural language” understood by the portalsoftware.

At step 185, control logic registers and confirms feasibility of theoriginal request. This step includes parsing the request, confirming apresentation option, confirming presentation delivery parameters(software, hardware, medium) and so on. Once a request is approved foraction, a data gatherer at step 187 accesses the database, such as inrepository 157 (FIG. 7) for required data. Such a gatherer, termed a botby the inventor, may be part of DBRE 155 as illustrated in FIG. 8, orpart of GSS 159 of FIG. 7.

At step 189 it is determined whether or not there is sufficient dataavailable in aggregation to complete the request. If the decision isyes, then the required data is extracted from the database (DB) in step191. At step 193 the extracted data is processed according to tools thataccomplish the user's request, which is a solution-orientated result.Text records of processing may also be forwarded to a user if requested.In this way a user might review several steps taken to arrive at asolution-oriented result.

At step 193, the raw result data is prepared according to user-requestedpresentation options in such as GUI module 181 of FIG. 8. A presentationoption may consist of simple text results appearing on a user's portalhome page. In one embodiment, a separate WEB page may be constructedthat displays varied versions of the same result such as a time chart, atext paragraph explaining the chart, and a table reflecting resultvalues. A meta-summary dealing with an averaged interest rate, asdescribed in an example above, may be presented in a variety of ways.For example, each account and individual result may be listed, followedby a summed result over a particular time span, followed by an averagefigure over a smaller increment of time. There are no limits topresentation possibilities as long as the appropriate softwarecontainers are supported at both ends of the interaction. In most cases,a browser interface supporting full interactive function will beutilized. In step 197, the prepared GUI data is sent to a requestinguser such as one operating PC 163 of FIG. 7 over an Internet connectionsuch as connection 161. It should be noted here again that many devicesare capable of effecting an interface with DBRE 155 of FIG. 8 andreceiving result data. The success of configuring varied devices to thesystem will depend on provided network and data interfaces.

If in step 189 it is determined that there is not enough data or theright kind of data already in aggregation to complete a request, thenthe request is passed over to a GSS, such as GSS 159 of FIG. 7 in step199. In one embodiment gathering is the sole responsibility of GSS 159as has already been described. In step 201 site logic templates areobtained from such as a KW operating a PC such as PC 167 of FIG. 7. Ifthe navigation templates required are the same as templates that havebeen previously used, then such templates may be obtained from aconnected data store.

At step 203, a GSS such as GSS 159 of FIG. 8 navigates to and extractsdata from required WEB sites in order to complete the aggregated datastore on behalf of the requesting user. At step 205, the data is passedinto aggregation in a database assigned for the purpose in such asrepository 157. After all of the required data has been aggregated instep 205, steps 191 through 197 are repeated.

It will be apparent to one with skill in the art that the process stepsdescribed above represent a mostly automated or completely automatedprocess. Moreover, there may be other sub-routines added withoutdeparting from the spirit and scope of the present invention such asadding a user notification step in the event that in step 189, data isinsufficient.

It will also be apparent to one with skill in the art that a processroutine such as the one described herein may be altered according to analternate operating environment without departing from the spirit andscope of the present invention. For example, if a user is interfacingfrom a wireless device through such as a data center network interface,then added steps may be required to convert data to a format understoodon a different network. There are many diverse applications.

FIG. 10 is a representative view of an actual screen shot 207 of ameta-summarized report 209 on display in a user's browser interfaceaccording to an embodiment of the present invention. In a more commonimplementation of the present invention, a user interfaces with such asa portal server by utilizing a common browser interface, many brands ofwhich are known in the art and readily available. In this particularexample, a Microsoft™ browser application known as the InternetExplorer™ (IE) is used. However the system of the present inventionworks with any software interface capable of navigating a data packetnetwork.

Summary report 209 consists of individual bank, investment and accountlistings complete with the names of the institutions. Summaries of theindividually reported information for both bank accounts and stockaccounts are found beneath each group listing. Report 209 is a rathersimplified example of many graphical possibilities and presentationmethods. Depending on the complexity of a request, a meta-summarizedreport may contain virtually any type of presentation mediums. Someexamples include, but the invention is not limited to limited to, Gantcharts, time graphs, pie charts, flow charts, text summaries, and so on.In another embodiment, a summarized report may contain interactiveoptions for looking at the same data in different ways, or evencalculating further results from the results presented. A user has manyoptions when accomplishing interface with the system of the presentinvention through a fully functional browser application installed on apowerful PC. Interface through other devices such as personal digitalassistant's, cellular telephones, and the like will obviously limitpresentation options, however, the use of such devices for interface ispossible and may, in some situations, be preferred. Such situations maybe business meetings, interviews, and other situations wherein a usermay need to access some summary data, but does not have access to hispersonal computer station. Moreover, such data may be previously orderedand sent to a place other than at his or her personal computer. Withappropriate interface to telephony networks, such information may, ifdirected by a user, be faxed to a meeting place, e-mailed to anassociate's e-mail address, and so on. There are many diverseapplications, many of which have already been stated.

Multiple Point-of-Access Summary Interface

According to a preferred embodiment of the present invention, aninteractive software interface suite is provided and packaged to enablemulti-point access to deeper levels of summary data as well astransaction and direct account access capabilities.

FIG. 11 is an exemplary screen shot of interactive interface suite 211for enabling multipoint account management capabilities according to anembodiment of the present invention. Interface suite 211, termed aDashboard by the inventors, provides a single interactive center forviewing summary data and for performing various transaction tasksrelated to data available through the interface. Interface 211 isdescribed as a suite because it is composed of a plurality ofsub-interfaces categorized in general by the type of data andfunctionality available through interaction with them. The plurality ofsub-interfaces forming interface 211 are, in this example, packaged inthe form of a single dynamic Web page using hyper-text-markup-language(HTML).

Referring now to FIG. 10, interface 211 replaces interfaces 207 as amore functional, organized, and user-friendly interactive interface forreceiving summary and solution-oriented data.

Referring now to FIG. 7, exemplary user 163 accesses services byinterfacing with portal interface 153 via Internet access line 161.Interface 211 is adapted to be served to user 163 in the form of a Webpage that his dynamic nature meaning that it is continually updated withnew information. Referring now to FIG. 8, database reporting-engine 155provides the data preparation and calculative services necessary forenabling the enhanced display capabilities of interface 211 and relatedsub-interfaces.

In this example, interface 211 is made up of 9 sub-modules each moduleproviding a different class of functionality. An Account Alerts module213 is provided within interface 211 and adapted to display varioustypes of user-configured alerts that may be applied to a wide range ofuser account types. A Net Worth module 215 is provided within interface211 and adapted to report a user's net worth information as determinedthrough calculation related to data associated with all of the user'sfinancially related accounts, assets, and financial activities. Module215 is illustrated in this example as presenting dynamic graphics in theform of pie charts describing a user's current assets and liabilities.

A bill Payment module 217 is provided within interface 211 and adaptedfor user configuration to report parameters related to bill payment. ACalendar module 219 is provided with interface 211 and adapted to holdall of a user's pending data-sensitive information. A Transaction Centermodule 221 is provided within interface 211 and adapted to list andsummarize all of a user's online and manually input transactions. ACommunications module 223 is provided within interface 211 and adaptedto report parameters associated with a user's online communicationsapplications.

An Account Bookmarks module 225 is provided within interface 211 andadapted to list all of a user's Web services in the form of hyperlinks,which are enhanced with automatic login functionality (known toinventor). A Portfolio Tracker module 227 is provided within interface211 and adapted to follow and report parameters related to the user'sfavorite stocks and other investment vehicles. A Travel Planning module229 is provided within interface 211 and adapted to enable a user toinitiate, create, and manage travel itineraries including all parametersrelated to ticket purchase, hotel accommodations, car rentals, and otherrelated tasks.

All of sub-modules 213-229 are interactive in the sense that a userinvokes each module in order to obtain more detailed informationregarding the types and classes of dynamic data handled by the invokedmodule. Therefore, data visible on the “face” of each module representsinitial summarized updates that are exploitable for further details.

In one embodiment, further interactive enhancement is included insub-modules 213-229 that list service providers maintaining accounts forusers. From within these modules, the actual login service pages ofthose entities are accessible through provision of the appropriatehyperlinks to those pages. In addition to providing direct access to auser's service-providing entities through modules 213-229, hyperlinks toone or more configuration utilities associated with one or more modulesservicing a particular class or type of data may also be provided.Another enhancement provided by interface 211 is that varioussub-modules exemplified herein are interlinked with each other throughdatabase reporting engine 155 of FIG. 8 such that they may shareoverlapping data and cooperate with each other in prioritized or otherfashions with regard to the presentation and reporting of data that maybe associated or linked to more than one of the individual modules.

Referring now back to FIG. 8, data input leading into request module 169of database reporting engine 155 may contain configuration input andrequest data from one or more utilities (not shown) that may, inpreferred embodiments, be accessible through interface 211 of FIG. 11.Output from GUI preparation module 181 is channeled for display into theproper sub-module or modules ordering the data. Any particular displaycharacteristics provided as options are stored in options database 173and the products of user pre-configuration.

Referring now back to FIG. 11, Account Alert module 213 informs a userupon initial display of interface 211 of, in this case, 5 new alertsrelated to various types of accounts. For example, a listed Wells Fargo™balance is shown to have dropped below a $200.00 balance threshold.Another listed alert informs a user that a Harry Potter© book orderedfrom Amazon™ has shipped. Alerts module 213 may be pre-configured toprovide virtually any type of time or event-sensitive alert that a usermay desire. By clicking on any of the listed alerts, a user may behyper-linked to the appropriate sub-module responsible for the detaileddata and account entity associated with the alert.

Net Worth module 215 uses the calculative and logic functions providedby database reporting engine 155 of FIG. 8 to present a periodic reportsummary of a user's current net worth. In this example, both assets andliabilities are graphically illustrated and color-coded to individualcategories of assets or liability. It is important to note herein, thatdata results presented in module 215 may be derived from virtually everyonline account accessible to a user through interface 211. In oneembodiment, the color-coded categories are interactive such that byclicking on them as hyperlinks sends a user to an appropriate sub-modulewherein more detailed information is provided. Also in this embodiment,by clicking on one of the graphics, a pop-up display containing detailedreport figures may be displayed. It is also noted herein, that all ofthe listed sub-modules 213-229 have interactive navigation arrowsinstalled on their faces, the arrows providing navigation to moredetailed levels of data which are displayed in secondary interfacesassociated with the main module invoked. More detail regarding Net Worthmodule 215 is provided later in this specification.

Bill Payment module 217 informs a user, in this example, that he or shecurrently has 8 bills due within the next 15 days. By clicking on theprovided navigation arrow, a more detailed account listing each bill byentity and account number and due date may be presented in a secondaryinterface associated with module 217. In this aspect, it is noted thatthe payment module 217 is interlinked with Calendar module 219 and mayshare overlapping data.

Calendar module 219 provides first, a summary of items to occur on theday accessed and items related to calendar events within the currentrunning week. By clicking on the navigation arrow provided, a secondaryinterface is served containing a more detailed calendar display. Moredetail about Calendar module 219 will be provided later in thisspecification.

Transaction Center module 221 informs a user of new transactionsoccurring since the last time of access. In this case there are twelvenew transactions noted. A maximum activity item is displayed on the faceof Transaction Center module 221 and related to a particular account, inthis case, a MasterCard™ account that has seen the most transactionactivity during a pre-configured timeframe, or since the last time ofaccess. Also shown on the face of Transaction Center module 221, is asection listing last transactions. In this action, there are twotransactions listed. A debit transaction is listed including an accountprovider and account number, the amount of the transaction, and the dateof the transaction. A credit transaction is listed that includes thesame account, amount, and date parameters of the debit transaction. Byclicking on the navigation arrow provided on the face of TransactionCenter module 221, a user may navigate to a secondary interfaceproviding additional detail. More detail about Transaction Center module221 will be provided later in this specification.

Communications module 223 alerts a user, in this case, of a quantity ofnew e-mails. In this case, there are fifteen new e-mails listed. In oneembodiment the fifteen e-mails listed may be generic to one e-mailaccount. In another embodiment, the fifteen e-mails listed may sourcefrom various accounts. By clicking on the navigation arrow onCommunications module 223, a secondary interface will appear containinglisted accounts. By clicking on one of the accounts listed, a user mayinvoke that particular e-mail interface and receive any associatede-mails through that interface. If only one e-mail account is configuredto Communications module 223, then clicking on the navigation arrow willsimply bring up that account software.

Account Bookmarks module 225 provides a list of URLs to a user'sregistered accounts along with a date listing the last time each accountwas accessed. By clicking on the navigation arrow provided on the faceof Account Bookmarks module 225, a user may invoke the secondaryinterface containing a more detailed rendering of account data.

Portfolio Tracker module 227 provides a summary view of the latestactivity regarding a user's chosen stock symbols. Module 227 alsoprovides a current summary regarding the top five stocks, in thisexample, contained in a user's stock portfolio. By clicking on thenavigation arrow provided on the face of Tracker module 227, a user mayinvoke the secondary interface rendering much more detail. Similarly,clicking on any of the listed stock symbols may invoke the secondaryinterface dedicated to that particular symbol, the interface containingmuch more information.

Travel Planner module 229 provides a tool for a user to invoke when itis desired to create travel plans. By clicking on the navigation arrowprovided on the face of the interface, a user may invoke a secondaryinterface containing a configuration utility for ordering and submittingtasks related to purchasing airline tickets, booking a hotel room,arranging a car rental, and any other travel related tasks. It is notedherein, that secondary interfaces associated with the above-describedmodules are, in many embodiments, utilities wherein a user may createand submit requests for task performance related to the class of datacovered by a particular module. In a preferred embodiment, such utilitytools enable proxy performance of online tasks. Still, hyperlinks toactual web sites may also be provided such that a user may navigate toand manually perform a task at the actual site invoked.

It will be apparent to one with skill in the art that interface 211 andassociated modules 213-229 may be provided of a different look and feelas well as of differing content and data classification withoutdeparting from the spirit and scope of the present invention. The uniquecapability loaded into interface 211 of enabling performance of variousproxy tasks, integrating solution-oriented data between more than onemodule of interface 211, and providing site-access to associated sitesthrough multiple points of entry represents a level of novelty not knownin current-art or prior-art interfaces. Furthermore, the unique proxycapabilities performed by the data compilation, aggregation, and summarysystem, known to the inventor, are fully accessible through interface211 providing a level of user-friendliness heretofore not known in theart.

FIG. 12 is an exemplary screen shot of a secondary interface 231 invokedas a result of user interaction with module 219 of FIG. 11 according toan embodiment of the present invention. Secondary interface 231 is adetailed calendar utility accessible by invoking Calendar module 219described in FIG. 11 above. Interface 231 is interactive according to avariety of provided options.

A resolution toolbar 235 is provided within interface 231 and adapted toenable a user to view various calendar resolutions of day, week, month,and year. In this example, interface 231 is displaying data associatedwith a particular calendar week (Jul. 18-24, 2000) as indicated.

A time-sensitive calendar bookmark window 237 is provided withininterface 231 and adapted to show the current day of the current monthof the current year. An interactive ad button 239 is provided withininterface 231 and adapted to enable a user to enter a new calendar itemsuch as an appointment, task, or other pending item. By invoking adbutton 239, an interactive utility (not shown) for making calendaradditions appears. Such utility contains all of the required fields anddialog options necessary for making correct calendar additions for laterdisplay within interface 231.

A show-item option window 241 is provided within interface 231 andadapted to enable a user to select specific categories of calendarentries to view within interface 231. In this example, the categoriesauctions, shopping, travel, bills, banking, credit cards, andinvestments are listed within window 241. The only category not selectedfor view is the category of banking Therefore, existing calendar entriesfor the remaining categories, which are selected, appear as visiblewithin interface 231. It is noted herein that calendar items pertainingto all selected categories within window 241 are restricted to itemspending within the week of Jul. 18-24, 2000 as ordered by the optionsselected in resolution toolbar 235.

A summary view section 233 is provided within interface 231 and detailsactual pending calendar items existing within the time frame of Jul.18-24, 2000 as ordered by window 241 and toolbar 235. In this example,the summary view lists the time and day of each pending item along witha summary description of each item. It is noted herein that titles ofentities associated to each pending item listed in section 233 areinteractive in that by clicking on them, further detail about thepending item is displayed.

Calendar interface 231, in a preferred embodiment, is cross-linked withother modules such that data incorporated therein may be affected byactions performed in other modules. For example, if a user pays a billthrough the payment module 217 of FIG. 11, and that particular bill waslisted as a pending calendar item within interface 231, then the actionof paying the bill through module 217 results in automatic deletion ofthe appropriate item entry in interface 231. Such interoperability isachieved through background application-program-interfacing (API) withdatabase reporting engine 155 of FIG. 8.

FIG. 13 is an exemplary screen shot of a secondary interface 243resulting from invocation of Transaction Center module 221 of FIG. 11according to an embodiment of the present invention. Interface 243 is aninteractive interface providing a more detailed summary view oftransaction data associated with a user's registered accounts. Interface243 may be thought of as an interactive utility that enables a user tocategorize all online transactions as well as off-line transactions intoa simple user interface. Interface 243 is both a summary reporting tooland a transaction entry utility.

It is noted herein that interface 243 is provided in the form of an HTMLinterface. In this example, all of the described interfaces aredisplayed as HTML interfaces. However, this is not specifically requiredin order to practice the present invention. Interface 211 of FIG. 11 andall associated interface modules and secondary interfaces may beprovided using other markup languages and programming techniques.Furthermore, much tailoring may be provided in order to adapt suchinterfaces to display in accordance to rules and protocols of a varietyof data-access devices. For example, scaled-down versions for devicesthat use web clipper applications and many browsers can be provided.

Referring now back to FIG. 13, New Transactions Summary window 245 isprovided within secondary interface 243 and adapted to displayquantities of new transactions categorized to associated accounts. Newtransactions are identified, in this example, as any new transactionsthat have occurred since the last time of update or sense the last timeof user access of interface 243. There are four accounts listed by titlewith each account associated with the specific quantity of associatednew transactions discovered.

A scroll-down menu 247 is provided within secondary interface 243 andadapted to list all of the user's registered accounts in an interactivefashion such that selecting one of the items contained in menu 247invokes a transaction history report exemplified herein by a historywindow 249. Therefore, in this example there are five transactionsassociated with the selected account (Chase™ Visa™ Credit). In thisexample, the five detailed account transactions listed in window 249 bythe five new transactions reported for the same account in window 245.It will be apparent to one with skill in the art that there may be moreregistered accounts listed in menu 247 than are shown in summary window245 without departing from the spirit and scope of the presentinvention. In this example, window 249 simply details new transactionsreported in window 245.

The above-described detail of the new transactions listed in window 249includes date, description, amount of transaction, and category. A userusing a scroll-down category menu containing a list of category optionsmay assign category detail associated with any transaction. In this way,transactions may be uniformly categorized for tax and otherorganizational purposes. Action items are also reported within historywindow 249 such as for deleting a transaction and for notification thatan e-mail regarding a specific transaction was sent to acertified-public-accountant (CPA) for tax or other accounting purposes.

Other interactive options provided within secondary interface 243include a manual delete option for manually deleting a transaction, andan archive access option for accessing archived transaction lists. Stillother options include CPA-notification option 251, a view-history option253, and a bill-payment option 255. Bill payment option 255 interlinkswith bill-payment module 217 of FIG. 11, which is a utility in enablinga user to perform online bill payment.

It will be apparent to one with skill in the art that interface 243 maybe provided of a different look, feel and function than that which isillustrated herein without departing from the spirit and scope of thepresent invention. For example, Summary window 245 may be adapted simplyto provide a pre-configured amount of latest transactions without regardto system update or user access. Similarly, Summary window 245 may listall of a user's registered accounts and quantities of latesttransactions instead of just those having new transactions discoveredsince a last update. Moreover, transactional histories may be organizedand accessible according to account, transaction category, and the like.

FIG. 14 is an exemplary screen shot of a secondary interface 257resulting from invocation of Net Worth module 215 of FIG. 11. Interface257 provides a more detailed view of a net worth report summarized withgraphic pie charts on the face of module 215 of FIG. 11. In this view,the graphic pie charts of module 215 are visible within a providedgraphics window 259. Window 259 represents a display option such as wasdescribed with reference to FIG. 8 and options a database 173. Othertypes of graphical representation may be utilized other than the piecharts exemplified herein. In this example, in addition to the piecharts and associated total figures, which are also represented on theface of module 215 as a summary view, actual percentages of data makingup the charts are included. An Asset-Allocation window 264 is providedwithin interface 257 and adapted to list all of the data categoriesassociated with asset computation and their respective totals. ALiability Mix window 263 is provided within interface 257 and adapted tolist all of a user's personal financial liabilities considered inassessing a total liability. As can be seen in this example, Windows 264and 263 are simply report mechanisms reflecting more detail associatedwith the graphic representation illustrated in window 259.

Net Worth interface 257 is a unique reporting vehicle that is able toprovide a user with up-to-date renditions of that user's current networth. Such a tool enables a user to modify his or her transactionalbehavior so as to benefit his or her total Net Worth. An interactiveHistory button 265 is provided within interface 257 and adapted toenable a user to view net worth history over a span of time. Such ahistory report may be presented in the form of a graph indicating valueon one axis and time on the other axis.

An interactive Financial Advice button 267 is provided within interface257 and adapted to enable a user to obtain financial advice in the formof system recommendations and/or advice from a live financial consultanthaving access to the user's portfolio and transactional data. Aninteractive Transfer Funds button 269 is provided within interface 257and adapted as a utility in enabling the user to engage in fundstransfer activity associated with registered accounts. It is notedherein that funds transfer activities initiated from invocation ofbutton 269 are assumed to be tasks that are performed by proxy. Althoughit is not illustrated in this example, invocation of Transfer Fundsbutton 269 provides an additional interface (not shown) that willcontain all of the necessary dialogue fields for facilitating transferof monies from one account to another. In one embodiment of the presentinvention invocation of Transfer Funds button 269 provides a list ofaccounts in the form of URLs. By clicking on these, a user may accessthose sites and perform manual transfer activities if so desired.

In one embodiment of the present invention, Net Worth module 215 of FIG.11 is cross-linked with other related modules such that active billpaying, online purchasing, and payment on loans is automaticallyincorporated into computations for net worth reporting. As was describedabove, solution-oriented results may be computed from and reported to avariety of the modules described in FIG. 11.

FIG. 15 is an exemplary screen shot of a Portfolio Tracker window 271resulting from invocation of Portfolio Tracker module 227 of FIG. 11.Interface 271 provides a more detailed rendition of the summaryinformation reported on the face of module 227 of FIG. 11. Aconsolidated portfolio listing 273 is provided within interface 271 andconsists of a user's stock symbols, company names, quantities of sharesowned, price of individual shares, and estimated value total for eachcompany. In this example, a solution-oriented result reflecting asummation of all of the estimated values of all of the owned stock isprovided as a total position value.

An individual-holdings window 275 is provided within interface 271 andadapted to enable a user to view individual stock or investment holdingsand also to navigate to actual sites maintaining the accounts asillustrated by the plurality of go buttons representing URLs. An optionswindow 279 is provided within interface 271 and adapted to enable a userto choose only the data that he or she desires to track and view.

It will be apparent to one with skill in the art that interface 211 asillustrated and described in this specification provides all of themechanisms for ordering, viewing, and manipulating all aspects ofonline, and some cases off-line user data through a single userinterface accessible from an Internet-capable appliance. Data accessiblethrough interface 211 is, in one embodiment, updated each time a user ofthe interface logs in. In another embodiment, data accessible throughinterface 211 is updated, in addition, by request termed a refreshaction in the art. In still other embodiments, portions of the dataaccessible through interface 211 are updated by demand while otherportions may be updated periodically. Still other portions of dataaccessible through interface 211 are continually updated in real-time.There are many possibilities.

It will also be apparent to one with skill in the art that interface 211and functional modules provided therein or accessed thereby may beinterfaced to a database reporting engine such as engine 155 of FIG. 8by, for example, API methods, or to equivalent software functioning asdatabase software resident on a machine having access to usersaggregated data.

Interactive Transaction Center Interface

According to a preferred embodiment of the present invention, aninteractive transaction center interface suite is provided and packagedto enable access to a multiplicity of data sources to provide detailedinformation, transaction capabilities, and direct account accesscapabilities.

FIG. 16 is an overview of a communications network 281 wherein anInternet portal system is practiced according to an embodiment of thepresent invention. This portal system, exemplified by specific equipmentgroupings and connection capabilities, is somewhat analogous to thecommunications network practicing an Internet portal system as describedin FIG. 1 of Ser. No. 09/208,740 referenced above in terms of basicarchitecture and software implementation.

Communications network 281 comprises basically an exemplary user,illustrated herein as operating a PC 283, an Internet access line 285,which connects user 283 to an illustrated Internet backbone 289, whichis illustrated as extending through the well-known Internet network 291represented in this embodiment as a cloud diagram 291. Furtherdescription will refer to user 283. Communications network 281, in thisembodiment, supports an Internet-service-provider (ISP not shown) inaddition to a unique network-portal capability, which will be describedfurther below.

User 283 is illustrated as a PC icon in this example, however in someembodiments, user 283 may access the portal system by means of anyInternet-capable device having a means for Internet access and displaycapabilities.

Internet access line 285 may be a normal telephone line, anintegrated-services-digital-network (ISDN) line, a digital subscriberline (DSL) or other well-known connection mediums including wirelessmediums. An ISP access architecture is described as a preferred means ofInternet access solely because of its commonality in the art. Apublic-switched-telephony-network (PSTN) may be assumed to be thenetwork through which user 283 accesses backbone 289. Backbone 289represents all of the lines, equipment, and connection points making upthe Internet network as a whole. Therefore, there are no geographiclimits to the practice of the present invention.

A service provider 293 is illustrated within Internet cloud 291. Serviceprovider 293 in this embodiment comprises a navigation server 295 and aportal server 297. Service provider 293 represents an entity providingdata procurement, aggregation, and summary services of personal on-linedata subscribed to by users. User 283, in this example, represents onesuch user subscribing to services provided through service provider 293.

Navigation server 295 is a unique information-source navigation serveradapted for the purpose of navigation to particular and/or designateddestinations on behalf of users. Portal server 297 hosts a uniquesubscription service as an Internet portal through which users may ordera wider variety of data procurement aggregation and summary services.Portal server 297 maintains all necessary passwords, user names, anduser profile data for the purpose of enabling proxy services. Therefore,a data repository for storing such information may be assumed to bepresent as was exemplified in FIG. 7 above regarding data repository157. Moreover, portal server 297 is analogous to the portal interface153 of FIG. 7. Navigation server 295 may be assumed to be analogous tothe gathering subsystem (GSS) 159 of FIG. 7.

Network 291, in addition to comprising service provider 293, alsocomprises a plurality of file servers located outside of the domain ofprovider 293. These servers are exemplified as a financial institutionserver 299, a utility company server 301, and an insurance companyserver 303. Servers 299-303 represent customer access points withinInternet 291 through which user 283 may access services. For example,user 283 may have one or more financial accounts accessible throughserver 299. User 283 may have an on-line utility account maintained byserver 301. User 283 may be assumed to have one or more insurancepolicies accessible through server 303. It should be noted herein, thatthe examples cited immediately above do not in any way limit the type,location, or number of information sources that are available to beaccessed within the scope of the present invention as practiced on theinternet. Internet network 291 is representative of a preferred use ofthe present invention, but should not be considered limiting, as theinvention could apply in other types of networks and combinations ofnetworks.

As taught by disclosure and example with reference to the applicationslisted in the cross-reference section of the specification, user 283 mayaccess Internet 291 by way to access line 285 and backbone 289 and thenengage in a data session with portal server 297 for the purpose ofordering a wide variety of tasks to be performed with respect to his orher personal data available in servers 299-303. Portal server 297 incooperation with navigation server 295 enables user 283 to managevarious aspects of his or her personal data held in servers 299-303without requiring user 283 to physically navigate to servers 299-303.The unique software suite described in the background section may beassumed in this example to be installed on portal server 297 andavailable to user 283 upon connection thereto. By virtue of thedescribed enhancement including interactive interface capability, a widearray of data management and task performance possibilities exist.

This specification focuses on a modular portion of the above describedsoftware suite termed a transaction center interface by the inventor.Therefore it may be assumed in this example that the above-describedsoftware suite, more specifically the transaction center module of thatsuite is displayed in the form of a personalized user interface on thedevice employed by user 283 to access portal server 297, which in thiscase is a PC. More detail regarding the innovative function of thetransaction center module of the present invention is provided below.

FIG. 17 is an exemplary screen shot of a personalized interactiveinterface suite 305 including a transaction center module 306 accordingto embodiment of the present invention. Interface suite 305 is analogousto the interface suite 211 illustrated in FIG. 11 above. Transactioncenter module 306 is analogous to the module 211 in the same figure.Transaction module 306 is adapted to enable proxy collection and displayof a multiplicity of subjects and for enabling multi-point transactionsof personal accounts according to embodiments of the present invention.

Transaction module 306 has a text summary on its face as well asinteractive icons, illustrated herein as a View Transactions icon 307and a Transfer Funds icon 309. By interacting with icons 307 and 309,which are HTML links in this example, a multiplicity of sub-interfacesrelated specifically to activities and history of financial relatedon-line accounts held by the interacting user (283) may be accessed. Ina preferred embodiment of the present invention, the main interface oftransaction module 306 is presented in HTML. Similarly, secondary orsub-interfaces accessible through interaction with HTML links 307 and309 are also HTML interfaces. However, the should not be construed as alimitation to the practice the present invention as other Web-baseddescriptor and markup languages may be provided with versions usable onvarying types of access devices. The example of HTML simply serves as astandard operating protocol for example of access through anInternet-connected PC as is the case with user 283.

Transaction module 306 provides information obtained from destinationsources related to the number and status of financial transactionsperformed by a user subscribing to the data. In this exemplary interfacethere are twelve new transactions noted as illustrated in a summary lineitem labeled New Transactions. A Maximum Activity notification is listedimmediately under New Transactions, and indicates that a major creditcard account that has been subjected to the most transaction activityduring a pre-established timeframe or since the last time of update ofthe transaction center module.

A Last Transactions section is illustrated within module 306 and listedtherein is a debit entry to a major banking institution and a creditentry to a on-line brokerage firm with the respective cash amounts anddates for those transactions. The text summaries illustrated on the faceof module 306 are assumed in this example to be ordered by therequesting user through pre-configuration to display at time of log-in.It is noted herein that there may be many varying descriptions andorders of summary data appearing on the face of module 306.

In the present embodiment, module 306 has at least two embeddedinteractive links as previously described, these being View Transactions307 and Transfer Funds 309. By interacting with View Transactions link307 on the face of the Transactions Center module 306, a user may accessmore detailed information about any one or all transactions availablefor viewing. By interacting with Transfer Funds link 309 on the face ofmodule 306, a user may engage in funds transfer activities associatedwith registered accounts. It is noted herein that funds transferactivities initiated from invocation of the Transfer Funds link areassumed to be tasks that are performed by proxy. Although it is notillustrated in this example, invocation of the Transfer Funds linkprovides an additional interface (not shown) that will contain all ofthe necessary dialogue fields for facilitating transfer of monies fromone account to another. Similarly, a secondary interface appears uponinvocation of link 307.

It will be apparent to one with skill in the art that text summaryinformation as well as embedded links 307 and 309 may vary in displayedlocation within module 306 without departing from the spirit and scopethe present invention. It will also be apparent that there may be moreinteractive links and more categories of text summary configured toappear on the face of module 306 at time of log in without departingfrom the spirit and scope the present invention. For example, the usermay configure additional summary information and categories as well as,perhaps, ordering one or more additional interactive links to beprovided with the initial summary interface (module 306). In thisregard, the real estate that module 306 commands with an interface suite305 may vary accordingly.

FIG. 18 is an exemplary screen shot of the Transaction Center caused todisplay through interaction with View Transactions button 307 of FIG.17. Transaction center interface 243 represents a secondary interfaceproviding a more detailed view of transactions as well as additionalinteractive options. In general, transaction center 243 enables a userto categorize completed credit card transactions, banking transactions,funds transfers, and person-to-person transactions, and potentiallyother transactions as well.

An accessing user can view and chart categorized transaction historiesover user-specified time periods. In this example center 243 displays adefault view illustrating a summary of new transactions (New TransactionSummary) and an all-accounts view of new transactions (New Transactions:All Accounts).

The New Transaction Summary window located furthest left withininterface 243 simply provides a more detailed summary of the twelvetransactions noted on the face of module 306 and FIG. 17. The NewTransactions window located adjacent to the summary window and to theright provides individual line items having various data aspectspresented in column form. Reading from left to right there is a columnfor the Date of each line item, a column for Description of each lineitem, a column specifying a debit Account for each line item, and acolumn specifying the Amount of each transaction.

An additional section is provided within interface 243 and labeledCategory. This section comprises a plurality of drop-down menus listinga plurality of transactions category options. These default categoriesare intelligent, in that transactions are automatically categorized withan appropriate category as they occur and are entered under theappropriate category based on a user's prior categorization scheme. Itis noted herein that a user may arbitrarily change a category associatedwith any line item by simply interacting with the drop-down menus suchas menu 315, and selecting an alternate category. Where transactionscannot be categorized automatically, they are listed uncategorized inthe default mode. Basic transaction categories may include, but will notnecessarily be limited to, Uncategorized, Income, and Expenses. Theincome category may include, but will not necessarily be limited to:Salary, Bonuses, Dividends, Gifts, Interest income, Investment income,Other income, and Tax refunds. The expenses category may include, butwill not necessarily be limited to: Auto, Bank, Cash, Charity, Clothing,Dining, Education, Entertainment, Gift, Groceries, Household, Insurance,Interest, IRA contribution, Medical, Miscellaneous, Recreation, Rent,Subscription, Taxes, Utility, and Vacation. By selecting one of thebasic categories, transactions are sorted and displayed according tothat category. By selecting one of the subcategories associated with thebasic category, transactions are sorted and displayed according to thatsubcategory.

In the New Accounts Summary window there are indicated 12 newtransactions having occurred on all accounts as previously described.Those accounts are listed below the 12 new transactions labeled and arenoted as five new transactions on a major banking institute credit card,three new transactions on a major bank savings account, two newtransactions on a checking account at that same major bank, and two newtransactions with an on-line brokerage firm. The entries in the NewTransactions Summary are interactive entries that upon interaction takethe user to another view or secondary interface. For example, if a userclicks on one of the interactive accounts listed in New Transactions,all transactions specific to the selection are displayed and listed inchronological order with the newest transactions at the bottom of thelist. The metamorphosis just described occurs within the newtransactions window. Therefore, the new transactions window acts as aresults interface capable of alternate displays according to userselection.

It is noted herein that “new transactions” are those transactions notyet viewed. Once a transaction has been viewed, it is moved to aTransaction History page (not shown) details of which are provided laterin this specification. In the New Transactions: All Accounts window theindividual transactions include the date, description, account, amount,and category of each individual transaction as previously describedabove. Transaction category display is tailored to the needs of a userthrough selection of one of the navigation arrows 315 for majorgroupings of subjects represented in this embodiment by Food andBeverage, Utilities, Home, Auto, and Charitable Organizations.

There are three functional links displayed on the face of interface 243.A Save Categories function 317 allows a user to select categoriesrelated to specific accounts and save them to be accessed as newtransactions occur. In one embodiment, a user may specifically createcategories for certain types of transactions. When new transactionsoccur, they are automatically categorized according to user preference.In a preferred embodiment however, most transactions can be associatedby default with one of the plurality of default categories available.

A transaction history function 319 is provided within interface 243 andadapted to enable a user to gain access to a secondary interface, whichprovides an uncategorized detailed history of transactions. In thismode, the user also has the ability to view transactions in amultiplicity of combinations of accounts, timeframes, and categories. Abill payment function 321 is provided within interface 243 and adaptedto enable a user to access the Bill Payment module depicted in FIG. 11and in FIG. 17. It is noted herein, and has been previously described,that the individual account entries displayed on the face of the NewTransactions: All Accounts window are interactive, such that byselecting any one of the individual accounts, a secondary interface isaccessed that will display all transactions associated with the selectedaccount.

FIG. 19 is an exemplary screen shot of a Transaction Center: One AccountView 323 which is reached by clicking on any one of the designatedaccounts highlighted in the New Transactions: All Accounts field of theTransaction Center—Default View 243 of FIG. 18. Interface 323 displaystwo windows. A New Transaction Summary is the same summary informationdisplayed in the Default View (243) of FIG. 18. The second window islabeled New Transactions and is specific to a single account, in thiscase a Chase™ Visa credit card account. The transactional informationdisplayed in the New Transactions window shows all the new transactionsrelated to the selected account. The window lists all the transactionsthat have taken place within a prescribed time period or since the lasttime a user has accessed the module.

In this example the account is for a major bank credit card as describedabove and lists five transactions that have occurred over a time periodof five days. The information displayed includes the date of thetransaction, a description of the entity with whom the transaction wasmade, the amount of the transaction, and the category associated withthe transaction. This screen shot also includes the previously describedfunction buttons Save Categories 317, Transaction History 319, and BillPayment 321. It is noted herein that the purpose of categorization ofall transactions can be used for all kinds of accounting purposes suchas automated tax preparation, business auditing, and forsolution-oriented summary reports specific to one or more category oftransactions.

FIG. 20 is an exemplary screen shot of the Transaction Center:Transaction History/All Accounts interface 324 which is accessed byclicking on the Transaction History button 319 FIG. 18 or FIG. 19.Transaction History interface 324 is a secondary interface that providesan expanded view of all transactions that have occurred over adesignated and selectable period of time of a user's on-linetransactional activity. The default display for interface 324 includesall transactions listed in chronological order for all registeredaccounts. In this example interface 324 includes three interactivedrop-down menus through which a user may choose to view historiesassociated with selected options. Account menu 325 includes all theaccounts that a user has included in his or her accounts managementprofile. Timeframe menu 327 enables a user to select a history timeperiod in graduated increments of YTD (Year to Date), this month, last 3months, last 6 months, last 12 months, and all history. It is notedherein that options for viewing all history and Last 3 months are notillustrated within timeframe window 327, but may be assumed to bepresent. Moreover, there may be many more timeframes for selectionwithin menu 327 that are illustrated without departing from the spiritand scope the present invention. Furthermore, a user may, throughpre-configuration, create specific and personalized timeframes forviewing transactional history.

Menu 329 enables a user to select a specific category of transactions toview in a transaction-history format. Selectable options within menu 329include but are not limited to a chronological view, view by category,and further options include each individual category that a user hasincluded in his or her accounts management profile. It is noted hereinthat any selection made with respect to windows 325-329 causes animmediate display of an associated history list in a transaction historywindow located just below the described menus. Through selecting variousentries in the above-described interactive menus, one is able to viewthe transaction histories in a multiplicity of combinations of accounts,time periods, and categories. Once a user has selected an entry in anyone of menus 325-329, an interactive display function 331 enablesrefreshing the transaction history list displayed in the all accountswindow according to the format dictated by the option selected.

In this example, the transaction window lists all user transactionschronologically and displays the date, description, category, account,and amount of the transactions. At the bottom of the transaction listingwithin the transaction history window is an accumulated expenses totalof the transactions displayed. The Transaction History/All Accountsscreen shot includes scroll button at the bottom of the screen thatallows the user to page to the next screen or return to the previousscreen in order to view all transactions over a given time period of thehistory of the account management. This example includes an EditCategories function 335 by which a user may edit the all accounts,chronological, and all history default pages to suit the needs of theuser. An additional feature in this example is provided in the form ofan interactive function enabling a user to chart results. An icon 333labeled Chart It enables this function. Chart It function 333, onceinvoked, enables a user to view solution-oriented charts detailingtransactions in a chart form rather than the tabular form as displayedherein. More detail regarding the function of the chart feature 333 isprovided later in this specification.

FIG. 21 is an exemplary view of an interface that displays TransactionHistory/All Accounts—by category: YTD 337. This example includes all ofthe elements and functions thereof described in FIG. 20 above. Thetransactions listed in the transaction history window in this exampleare formatted differently than those listed in the transaction historyof interface 324 of FIG. 20. In this example, transactions of all useraccounts are presented by category. This presentation format is achievedby selecting the All Accounts option in menu 325, the By Category optionin menu 329, the YTD option in sub-module 327, and than invoking Displaybutton 321. The data displayed in the transaction history window isformatted according to all three selections as is illustrated in thisexample.

In a preferred embodiment, many combinations of displayable formats areachievable according to variable selection performed with regard tomenus 325-329. For example, by selecting All Accounts in menu 325, last6 months in menu 327, Auto in menu 329, and then invoking Display button321, the data presented in the transaction window would reflect only thefirst two line items currently displayed. Through the selection of anynumber of combinations of entries in the three drop-down menus, a useris able to format the data presented in the transaction history windowin a manner that specifically suits the user's needs. In this example,transactions displayed by category in the transaction history window aresupplemented with a total dollar amount by category reported beneatheach category. Similarly a YTD expense total is calculated and providedat the bottom of the window. As noted above, Edit Categories button 335located at the bottom of the transaction history window enables a userto tailor the categories for desired interaction with the accountsselected.

FIG. 22 is an exemplary screen shot of a Transaction History/Bar Graph339 displayed as a result of user interaction with Chart It icon 333 ofFIGS. 20 and 21. It is noted herein that the bar graph illustrated inthis example appears within the real estate occupied by the transactionhistory window described in interfaces 324 and 337 of FIGS. 20 and 21respectively. In one embodiment, only the transaction-window of thedescribed interfaces actually refreshes with new data in the fashion ofa results window. However, different element numbers are applied to eachrepresented interface to illustrate a new interface having new datadisplayed therein as may also be the case in some embodiments.

Interface 339 retains elements 325-329 and icon 341 described in earlierinterfaces. In this example, the bar chart represents data calculatedand displayed in bar sections representing transaction totals of allaccounts, by month, over the last four months. Colors may be used, andthe colors used are keyed in a display beside the bar graph. The barchart representation may be displayed in any of the multiplicity ofcombinations of selected options available from the three drop-downmenus, 325, 327, and 329. It is noted herein that a user may order chartcalculation and preparation through previously described icon 333.Display graph icon 341 is intended, in this example, to refresh a samechart configuration that is altered by changes in option section asperformed by a user with respect to the options listed in drop-downmenus 325-329.

By selecting options in one or more of drop-down menus 325-329, and theninvoking display graph icon 341, the real estate of the bar chart areais refreshed and displays a revised bar chart of the same generaldescription indicating the selections of the user. For example,selection combinations may include the last six months of auto expensespaid from all accounts, this month's entertainment expenses paid from aspecific bank checking account, or perhaps, the last 12 month's expensespaid from a major credit card for entertainment. An interactive Closeicon is provided at the bottom of interface 339 to enable closing ofinterface 339 upon user invocation thereof.

FIG. 23 is an exemplary screen shot of a Transaction History/Line Graphinterface 343. It is noted herein and was described above, that in apreferred embodiment interaction with Chart It icon 333 of FIG. 21enables chart calculation and preparation according to a generalgraphics format chosen by a user. Instead of a bar chart, this exampleillustrates a line graph as a pre-configured choice of graphics display.Within interface 343, the exemplary line graph illustrates data showinga plotted transaction total of entertainment transactions plotted bymonth with the totals of 4 months visible. As described above withrespect to FIG. 22, the chart display may be modified by selecting anyone of the combinations of options provided in the three drop-down menus325, 327, and 329 and then invoking display graph icon 341. Such dataalterations may reflect user choices to display the transaction totalsof a major credit card, a bank checking or savings account, or any ofthe other listed accounts specified to be included in account managementcapability. In the same manner just-described, options may be selectedto cause display of a line graph of auto expenses over time, charitableexpenses for the last 12 months, food and beverage over the last sixmonths, or any other selectable combinations that may be displayed as aline graph.

It will be apparent to one with skill in the art that the transactioncenter module of FIG. 17 as illustrated and described in thisspecification provides all the mechanisms for summarizing, tracking,categorizing, listing, and charting any and all transactions designatedby a user to be included in the accounts management functionality of asingle user interface accessible from an Internet-capable appliance. Theinformation and history provided through the transaction center moduleof the present invention is updated and available to the user each timethe user accesses the module and operates through the various secondaryinterfaces described. In various embodiments, data viewable through thetransaction center module is updated by a request-refresh action,through on-demand ordering, through periodic push of data and in realtime as transactions occur and are detected. There are many and variedpossibilities.

It will also be apparent to one with skill in the art that thetransaction center module and functional sub-interface accessibletherefrom may be interfaced with a database reporting engine such asengine 155 of FIG. 8 by API or other methods, or to equivalent softwarefunctioning as database software resident on a machine having access touser's aggregated data and account information.

The method and apparatus of the present invention may be practiced viaprivate individuals on the Internet, businesses operating on a WANconnected to the Internet, businesses operating via private WAN, and soon. There are many customizable situations. The present invention astaught herein and above should be afforded the broadest of scope. Thespirit and scope of the present invention is limited only by the claimsthat follow.

1. A method for sorting and presenting financial data, comprising thesteps of: (a) using a computerized appliance, gaining access to a firstnetwork site; (b) using an interactive interface at the first networksite, accessing financial data at one or more second network sitesstoring financial information associated with a particular person; (b)specifying through the interactive interface a category of data and atime frame; (c) retrieving data from the one or more sites according tothe category and time frame specified; and (d) summarizing anddisplaying, at the computerized appliance, the data retrieved throughthe interactive interface.
 2. The method of claim 1, wherein thedata-packet-network is the Internet network.
 3. The method of claim 2wherein in step (b), the interactive interface is ahyper-text-markup-language interface served by a portal server connectedto the network.
 4. The method of claim 1 wherein in step (a), thecomputerized appliance is a personal computer with connection to thenetwork.
 5. The method of claim 1 wherein in step (a), the computerizedappliance is a cellular telephone with connection to the network.
 6. Themethod of claim 1 wherein in step (a), the computerized appliance is ahand-held computer with accessibility to the network.
 7. The method ofclaim 1 wherein in step (b), the category of data includes one ofsalary, bonus, interest income, food and beverage, utility payments,home, auto, charitable contribution, or entertainment.
 8. The method ofclaim 1 wherein in step (d), an option is provided for presenting thedata in a graphic format.
 9. The method of claim 1 wherein a step isprovided linking the interactive interface to an interactive bill payingmodule.
 10. The method of claim 9 wherein a further step is provided forlinking the interactive interface to an interactive transfer-fundsinterface for transferring funds between financial accounts.